Handle malformed data in results
Opened this issue · 0 comments
schneems commented
Need a parser that can accommodate this:
3.635861 0.271070 3.957706 ( 4.451950)
3.658097 0.259989 3.956018 ( 6.375668)
3.645830 0.300098 3.985729 ( 4.479861)
3.717054 0.257627 4.012474 ( 4.437075)
3.518767 0.284179 3.850532 ( 4.533361)
3.647776 0.250607 3.949652 ( 6.333169)
3.650700 0.255125 3.944806 ( 4.331832)
3.599905 0.248381 3.890607 ( 4.270693)
3.589013 0.248963 3.882700 ( 14.741302)
3.549133 0.243314 3.831065 ( 4.752615)
3.637030 0.265008 3.938134 ( 4.583956)
3.707378 0.262794 4.010824 ( 14.491934)
3.600069 0.251012 3.887343 ( 4.750288)
3.614917 0.281785 3.935370 ( 4.726997)
3.614017 0.245371 3.895933 ( 7.255681)
3.513302 0.241565 3.791374 ( 4.597545)
3.481929 0.237348 3.764888 ( 4.127399)
3.681426 0.257285 3.976662 ( 4.760247)
3.651148 0.263395 3.952579 ( 5.545362)
3.450599 0.242363 3.728665 ( 4.137846)
3.468851 0.249998 3.766952 ( 4.134255)
</html>
3.608046 0.259281 3.906391 ( 4.704833)
3.695854 0.261036 3.993135 ( 4.539016)
3.474631 0.237228 3.747401 ( 4.112216)
3.658769 0.261520 3.960668 ( 4.828371)
3.520887 0.236373 3.797928 ( 4.165172)
3.461020 0.242898 3.744059 ( 4.146483)
I think this happens when i'm running a benchmark and my computer goes to sleep and then I wake it up again, but i'm not sure. I guess if that's the case i'm not sure if we should abort or plow through.