WineTest failure patterns
Zebediah Figura (she/her)
zfigura at codeweavers.com
Thu May 27 11:06:54 CDT 2021
On 5/27/21 9:45 AM, Francois Gouget wrote:
>
> The new "failure patterns" pages are now complete:
>
> * All results
> https://test.winehq.org/data/patterns.html
> * TestBot's Windows VMs only
> https://test.winehq.org/data/patterns-tb-win.html
> * TestBot's Wine VMs only
> https://test.winehq.org/data/patterns-tb-wine.html
>
>
> The main additions are:
>
> * The pages start with a bit of documentation.
>
> * Before the tests there is now an 'overview' pattern showing the number
> of failed test units for each machine. This is useful to detect when a
> VM goes bad, for instance when Windows 10 decides to pop up a 'first
> use' configuration dialog: that line will turn red. This can also
> highlight machines that get worse results than their peers, and thus
> warrant a check.
> You will also notice a couple of machines that only have a handful of
> failures!
>
> * For each test the pages link to related commits. For each commit they
> show if it modified the test itself, a shared test resource or the
> Wine module. This simplifies reviewing potential culprits when a test
> starts failing.
>
> * For each test the pages link to the related bugs. This simplifies
> checking if someone has already analysed the bug or tried fixing it.
> If the bug has a regression commit id, that commit is also shown as
> such.
>
> * The page also shows bugs for tests that have no failure. This
> simplifies verifying that the bugs have been closed when a test is
> fixed.
>
>
Nice, thanks for setting this up!
More information about the wine-devel
mailing list