[Fuego] Status update for Fuego

Bird, Timothy Tim.Bird at sony.com
Mon Aug 28 06:21:38 UTC 2017

> -----Original Message-----
> From: Daniel Sangorrin on Sunday, August 20, 2017 7:42 PM
> > -----Original Message-----
> > From: Bird, Timothy on Friday, August 18, 2017 9:12 AM
>  ...
> > Also, plotting seems to be broken at the moment.  When Daniel
> > gets back into town maybe he can take a look at this.
> I'm back into town, although I will be quite busy this and next month.
> About plotting, we had 2 types of plotting:
>   - the plot.png generated, mostly for benchmark tests, with matplotlib.
>   - the interactive plots made with the flot javascript library
> My plan is to move the matplotlib plots to the ftc gen-report command.
> I need to think about how to integrate that with the current interface.
> About the interactive plots, I have disabled them in favor of the HTML
> reports.
> # The plotting code is still there in mod.js but temporarily disabled.
> One of the reasons I left it disabled was that despite for simple tests the
> interactive plots where
> fine, tests with many test_cases and measures required at least as many
> interactive
> plots and that caused a rather high overhead on my browser.
> Do you want the interactive plots back in addition to the HTML tables output?

With LTP output fixed, the HTML tables are now taking a really long time to render
in the Jenkins interface.  Ultimately, I'd like there to be a default view of either
table or plot, that is selected by a configuration item in the test directory.  This could
be customized by the user, if they want to see different data, or change the format.

We'll have to make some modification to the system before the 1.2 release.  LTP
is unusably slow in the current configuration.  So maybe at least we need
to specify a subset of items to view, or just show an aggregate count, with a list
of up to 10 items that failed, or something, in the HTML table.  I don't know what the
solution is yet.  I worked on LTP criteria handling last Friday and Saturday, and didn't
get as far with other stuff as I had hoped.

I'll let you know what I think when I work on it a bit more this week.
 -- Tim

More information about the Fuego mailing list