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 http://testbot.winehq.org/JobDetails.pl?Key=2036
Your paranoid android.
=== W98SE (32 bit process) === Failure running script in VM: Exceeded timeout limit of 315 sec
On 05/13/2010 01:54 AM, (Marvin) wrote:
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 http://testbot.winehq.org/JobDetails.pl?Key=2036
Your paranoid android.
=== W98SE (32 bit process) === Failure running script in VM: Exceeded timeout limit of 315 sec
Hi,
This is a false positive. The Win9x kernel32 tests have always shown such behavior. This of course needs to be fixed but has nothing to do with this patch. Notice the "kernel32:process done (0)" in the log for Win98.
I'm not sure if this behavior is caused by the tests themselves or whether it's caused by some interaction issues when run from a command prompt (or batch file like WTB is doing).