test.winehq refactoring

Huw Davies huw at codeweavers.com
Mon Apr 3 09:56:35 CDT 2017

> On 2 Apr 2017, at 20:51, Francois Gouget <fgouget at codeweavers.com> wrote:
>   - Provide per machine results over time.
>     The index files make it possible to see how the number of failures 
>     evolved over time for a fiven platform, such as Windows XP. But 
>     anyone running the tests regularly on a machine would appreciate 
>     being able to see how it fared over time. However that's currently 
>     impossible since you only get specific machine results on a 
>     per-build basis. A fix for that would be to add a 'flat all 
>     machines' top-level index, as well as 'flat all machines' indexes 
>     for each test unit.
>     https://bugs.winehq.org/show_bug.cgi?id=39379

This would be really useful for tracking regressions.

Something else that would be very useful is the ability to
display just the test bot VMs.  These are the ones we care
about the most, and the ones that are possible to fix without
having to get a third-party to manually run a test.  I find it
difficult to just keep track of these VMs when their results get
swamped by all the other machines’ failures.

I‘d imagine this should be possible to do using static
pages.  The root page (equivalent to data/index.html)
could be something like data/wtb_index.html.  Clicking
on a build id would take you to data/build-id/wtb_index.html,
then clicking on an OS flavour would take you to
data/build-id/wtb_index_flavour.html.  You’d also need some
way to toggle in and out of the mode.

Does that sound possible?


More information about the wine-devel mailing list