[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: kernel32/tests: Update trace message to report actually used timeout value.
From:       Marvin <testbot () winehq ! org>
Date:       2013-10-28 8:34:08
Message-ID: E1VaiH2-0007s8-Qk () wine ! codeweavers ! com
[Download RAW message or body]

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

Your paranoid android.


=== w2008s64 (32 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 1500)
comm.c:886: Test failed: WaitCommEvent used 1513 ms for waiting
comm.c:1551: test_AbortWaitCts timeout 500 handle 000000C4
comm.c:1518:  Changing CommMask on the fly for handle 000000C4 after timeout 500


[prev in list] [next in list] [prev in thread] [next in thread]