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=11654
Your paranoid android.
=== wvistau64 (32 bit events) === events.c:939: Test failed: unexpected call img_onerror
=== w7u (32 bit events) === events.c:939: Test failed: unexpected call img_onerror The test timed out
On 02/21/2015 06:18 PM, 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 https://testbot.winehq.org/JobDetails.pl?Key=11654
Your paranoid android.
=== wvistau64 (32 bit events) === events.c:939: Test failed: unexpected call img_onerror
=== w7u (32 bit events) === events.c:939: Test failed: unexpected call img_onerror The test timed out
That seems to be a fluke as a rerun of the tests passed on those machines https://testbot.winehq.org/JobDetails.pl?Key=11663
Ignore the w2000pro and w2003std failures as those are permanent issues unrelated to my patch. That's why Marvin didn't complain about those.
bye michael
-
Marvin -
Michael Stefaniuc