Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=113591
Your paranoid android.
=== w7u_adm (32 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 1498 ms for waiting
=== w7u_el (32 bit report) ===
kernel32: comm.c:886: Test failed: WaitCommEvent used 1498 ms for waiting
=== 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 1500 ms for waiting
=== w1064v1809 (64 bit report) ===
kernel32: comm.c:1586: Test failed: Unexpected time 265, expected around 500
=== w7u_2qxl (32 bit report) ===
kernel32: debugger.c:1027: Test failed: ole32.dll was not reported debugger.c:2122: Test failed: NtSetInformationDebugObject failed c0000008
=== w7u_adm (32 bit report) ===
kernel32: debugger.c:1027: Test failed: ole32.dll was not reported
=== w7u_el (32 bit report) ===
kernel32: debugger.c:1027: Test failed: ole32.dll was not reported
=== w1064 (32 bit report) ===
kernel32: debugger.c:681: Test failed: debugger reported 7 failures
=== w1064_tsign (64 bit report) ===
kernel32: debugger.c:1760: Test failed: unexpected instruction pointer 00007FFEE4AACE54
=== w1064v1507 (64 bit report) ===
Report validation errors: kernel32:module crashed (c0000005)