kernel32/tests: Fix the test_waittxempty() timeout.

Marvin testbot at winehq.org
Wed Oct 2 07:52:44 CDT 2013


Hi,

While running your changed tests on Windows, 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://newtestbot.winehq.org/JobDetails.pl?Key=2434

Your paranoid android.


=== wxppro (32 bit comm) ===
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
No test summary line found
Failure running script in VM: network read timed out

=== w2008s64 (32 bit comm) ===
comm.c:1670: test_AbortWaitCts timeout 500 handle 000000C4
comm.c:1637:  Changing CommMask on the fly for handle 000000C4 after timeout 500
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
No test summary line found
Failure running script in VM: network read timed out

=== w7pro64 (32 bit comm) ===
comm.c:1670: test_AbortWaitCts timeout 500 handle 00000130
comm.c:1637:  Changing CommMask on the fly for handle 00000130 after timeout 500
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1094: Test failed: WriteFile failed with a timeout
comm.c:1096: Test failed: GetOverlappedResult reported error 996
comm.c:1097: Test failed: expected 64000, written 0
Timeout

=== w2008s64 (64 bit comm) ===
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
Timeout

=== w7pro64 (64 bit comm) ===
comm.c:887: WaitCommEvent for EV_TXEMPTY took 0 ms (timeout 1000)
comm.c:1670: test_AbortWaitCts timeout 500 handle 00000000000000CC
comm.c:1637:  Changing CommMask on the fly for handle 00000000000000CC after timeout 500
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:1064: Test failed: WaitCommEvent failed with a timeout
comm.c:1075: recovering after WAIT_TIMEOUT...
comm.c:1086: Test failed: WaitCommEvent error 0
comm.c:1087: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
Timeout



More information about the wine-devel mailing list