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