[Fuego] bonnie fixup commit in Fuego pull request

[Bird, Timothy]

> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> 
> > -----Original Message-----
> > From: Bird, Timothy [mailto:Tim.Bird at sony.com]
> > Sent: Wednesday, September 06, 2017 12:39 PM
> ...
> > For the second issue addressed by the commit:
> > In general it seems correct to remove the latency measures, since they are
> not in the testlog output that I can see, and they certainly
> > are not parsed by the parser for this Benchmark.  The name change from
> Random_Seek.Random_Seek to Random.Seek is also
> > appropriate, but there needs to be a change to the name in the
> measurements dictionary in parser.py to match.
> 
> Sorry, I haven't been able to review the patch. I just wanted to say that
> certain measures will or will not be in the log depending on
> the spec but also on the board itself.

I figured this might be the case - that the latencies were not in the test log
results that I saw.

However, the bonnie parser.py doesn't have code to parse any latencies
at all from the bonnie test log.  Perhaps this was intended as an extension
to the bonnie parser in the future?

In any event, since they can never appear in a run.json file with the current
parser, I think the right thing is to remove the latency fields from the
reference.json file for now.  If we change the parser in the future, we can
modify the reference.json file to match.
 -- Tim