Signed-off-by: Jacek Caban jacek@codeweavers.com --- v2: Better timeout handling
dlls/kernel32/tests/debugger.c | 270 ++++++++++++++++++++++++++++++--- 1 file changed, 248 insertions(+), 22 deletions(-)
Hi,
While running your changed tests, 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=54414
Your paranoid android.
=== w7u (32 bit report) ===
kernel32: debugger.c:551: Test failed: debugger reported 2 failures
Jacek Caban jacek@codeweavers.com writes:
Signed-off-by: Jacek Caban jacek@codeweavers.com
v2: Better timeout handling
dlls/kernel32/tests/debugger.c | 270 ++++++++++++++++++++++++++++++--- 1 file changed, 248 insertions(+), 22 deletions(-)
It doesn't work here:
../../../tools/runtest -q -P wine -T ../../.. -M kernel32.dll -p kernel32_test.exe debugger && touch debugger.ok debugger.c:653: Tests skipped: "none" debugger test needs user interaction debugger.c:975: Test failed: dwDebugEventCode = -1 debugger.c:976: Test failed: ExceptionCode = 0 debugger.c:1013: Test failed: dwDebugEventCode = 1 debugger.c:1018: Test failed: didn't get any child events (flag: 1). debugger.cdebugger.c:149: Test failed: wrong size for 'C:\users\julliard\Temp\wtf1ab.tmp': read=0 debugger.c:963: Test failed: unexpected event pid debugger.c:975: Test failed: dwDebugEventCode = -1 debugger.c:976: Test failed: ExceptionCode = 0 debugger.c:1013: Test failed: dwDebugEventCode = 1 debugger.c:149: Test failed: wrong size for 'C:\users\julliard\Temp\wtf2a2.tmp': read=0 debugger.c:963: Test failed: unexpected event pid debugger.c:975: Test failed: dwDebugEventCode = -1 debugger.c:976: Test failed: ExceptionCode = 0 debugger.c:1013: Test failed: dwDebugEventCode = 1 debugger.c:149debugger.c: Test failed: :wrong size for 'C:\users\julliard\Temp\wtf394.tmp': read=0 debugger.c:286: Test failed: unexpected event pid make: *** [Makefile:347: debugger.ok] Error 16
On 7/3/19 11:17 PM, Alexandre Julliard wrote:
Jacek Cabanjacek@codeweavers.com writes:
Signed-off-by: Jacek Cabanjacek@codeweavers.com
v2: Better timeout handling
dlls/kernel32/tests/debugger.c | 270 ++++++++++++++++++++++++++++++--- 1 file changed, 248 insertions(+), 22 deletions(-)
It doesn't work here:
../../../tools/runtest -q -P wine -T ../../.. -M kernel32.dll -p kernel32_test.exe debugger && touch debugger.ok debugger.c:653: Tests skipped: "none" debugger test needs user interaction debugger.c:975: Test failed: dwDebugEventCode = -1 debugger.c:976: Test failed: ExceptionCode = 0 debugger.c:1013: Test failed: dwDebugEventCode = 1
This looks like the timeout needs adjustment. In this case timeout should be considered a failure, so we may just use a use a high value. I will send a new version.
Thanks,
Jacek