Re: [3/4] kernel32/tests: WaitCommEvent may sometimes return immediately on a busy system when write operation to a COM-port

[Marvin]

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=3039

Your paranoid android.


=== w2008s64 (64 bit comm) ===
comm.c:885: WaitCommEvent for EV_TXEMPTY took 1513 ms (timeout 1000)
comm.c:886: Test failed: WaitCommEvent used 1513 ms for waiting

=== w7pro64 (64 bit comm) ===
comm.c:859: Test failed: WaitCommEvent failed with a timeout
comm.c:870: recovering after WAIT_TIMEOUT...
comm.c:880: Test failed: WaitCommEvent error 0
comm.c:881: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:885: WaitCommEvent for EV_TXEMPTY took 1513 ms (timeout 1000)
comm.c:886: Test failed: WaitCommEvent used 1513 ms for waiting
comm.c:1552: test_AbortWaitCts timeout 500 handle 0000000000000068
comm.c:1519:  Changing CommMask on the fly for handle 0000000000000068 after timeout 500