On Thu, 21 Nov 2019, Marvin wrote: [...]
=== w1064v1809 (32 bit report) === === w1064v1809_zh_CN (32 bit report) === === w1064v1507 (64 bit report) ===
kernel32: comm.c:859: Test failed: WaitCommEvent failed with a timeout comm.c:880: Test failed: WaitCommEvent error 0 comm.c:881: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:886: Test failed: WaitCommEvent used 1516 ms for waiting
These are preexisting random failures: https://bugs.winehq.org/show_bug.cgi?id=47873
I suspect they are caused by the same issue the one below. Having the TestBot better deal with random failures would help but the call duration (1500, 1516 ms) may make it harder for the TestBot to identify them as preexisting failures. Maybe such values should be clearly identified, for instance by enclosing in double braces "used ((1500)) ms" so the TestBot would know to ignore that part when comparing failures.
=== debian10 (32 bit Japanese:Japan report) === === debian10 (32 bit Chinese:China report) ===
kernel32: comm.c:918: Test failed: OutQueue should not be empty
This one is also a known failure. It happens because QEmu ignores the serial port's baud rate: https://bugs.winehq.org/show_bug.cgi?id=48108