Hi,
It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=124678
Your paranoid android.
=== w7u_adm (32 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1514 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w864 (32 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1500 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064v1809 (32 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1500 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064 (32 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1500 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064_tsign (32 bit report) ===
kernel32: comm.c:1591: Test marked flaky: Unexpected time 328, expected around 500
Report validation errors: kernel32:comm returned success despite having failures
=== w864 (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1516 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064v1809 (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1500 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064 (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1500 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064_2qxl (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1500 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064_adm (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1515 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w1064_tsign (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1516 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w10pro64_en_AE_u8 (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1516 ms for waiting
Report validation errors: kernel32:comm returned success despite having failures
=== w10pro64_ar (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1516 ms for waiting
Report validation errors: kernel32:comm returned success despite having failures
=== w10pro64_ja (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1500 ms for waiting
Report validation errors: kernel32:comm has unaccounted for failure messages kernel32:comm returned success despite having failures
=== w10pro64_zh_CN (64 bit report) ===
kernel32: comm.c:860: Test marked flaky: WaitCommEvent failed with a timeout comm.c:882: Test marked flaky: WaitCommEvent error 0 comm.c:884: Test marked flaky: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:890: Test marked flaky: WaitCommEvent used 1515 ms for waiting
Report validation errors: kernel32:comm returned success despite having failures