http://bugs.winehq.org/show_bug.cgi?id=32003
Bug #: 32003 Summary: Properly account for WineTestBot errors Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs@winehq.org ReportedBy: fgouget@codeweavers.com Classification: Unclassified
Sometimes a test cannot be run on a Windows VM for a reason internal to WineTestBot rather than due to the patch author. This can be due to a WineTestBot bug or due to an administrator error. For instance: * A Linux VM that got declared as a Windows one. * TestAgentd was not started on the VM. * The VM is not reachable because it has the wrong IP address or some such.
In those cases WineTestBot entirely reports something like this in the log: * Can't copy exe to VM (Bad IP address) * Child process died unexpectedly (Linux VM used as a Windows one)
And yet on the summary page it shows 'completed - 0 failures'. Instead the summary page should either show something like 'completed with errors - 0 failures' or 'completed - 1 failures' so one knows something is wrong.