Re: kernel32/tests: Attempt to avoid timeouts by increasing the baud rate.

[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://testbot.winehq.org/JobDetails.pl?Key=15126

Your paranoid android.


=== w2000pro (32 bit comm) ===
comm.c:1552: test_AbortWaitCts timeout 500 handle 00000368
comm.c:1519:  Changing CommMask on the fly for handle 00000368 after timeout 500

=== w2008s64 (32 bit comm) ===
comm.c:861: Test failed: WaitCommEvent failed with a timeout
comm.c:872: recovering after WAIT_TIMEOUT...
comm.c:882: Test failed: WaitCommEvent error 0
comm.c:883: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:887: WaitCommEvent for EV_TXEMPTY took 1500 ms (timeout 1500)
comm.c:888: Test failed: WaitCommEvent used 1500 ms for waiting
comm.c:1552: test_AbortWaitCts timeout 500 handle 000000BC
comm.c:1519:  Changing CommMask on the fly for handle 000000BC after timeout 500

kernel32/tests: Attempt to avoid timeouts by increasing the baud rate.

[Huw Davies]

On 8 Jul 2015, at 00:12, Marvin wrote:
> === w2000pro (32 bit comm) ===
> comm.c:1552: test_AbortWaitCts timeout 500 handle 00000368
> comm.c:1519:  Changing CommMask on the fly for handle 00000368 after timeout 500
>
> === w2008s64 (32 bit comm) ===
> comm.c:861: Test failed: WaitCommEvent failed with a timeout
> comm.c:872: recovering after WAIT_TIMEOUT...
> comm.c:882: Test failed: WaitCommEvent error 0
> comm.c:883: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
> comm.c:887: WaitCommEvent for EV_TXEMPTY took 1500 ms (timeout 1500)
> comm.c:888: Test failed: WaitCommEvent used 1500 ms for waiting
> comm.c:1552: test_AbortWaitCts timeout 500 handle 000000BC
> comm.c:1519:  Changing CommMask on the fly for handle 000000BC after timeout 500

It seems testbot was teasing me.  Please ignore this patch.

Huw.