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=13201
Your paranoid android.
=== w2000pro (32 bit) === No test summary line found
=== wxppro (32 bit) === No test summary line found
=== w2003std (32 bit) === No test summary line found
=== wvistau64 (32 bit) === No test summary line found
=== w2008s64 (32 bit) === No test summary line found
=== w7u (32 bit) === No test summary line found
=== w8 (32 bit) === No test summary line found
=== wvistau64 (64 bit) === No test summary line found
=== w2008s64 (64 bit) === No test summary line found
Hi,
the tests here are only failed because no cmd argument was set:
"jscript: start - - Usage: C:\jscript_test.exe test_name
Valid test names: activex caller jscript run jscript: done (1)"
I tested the test successfully previously with the right argument:
https://testbot.winehq.org/JobDetails.pl?Key=13063
Regards
Am 03.05.2015 um 22:08 schrieb Marvin:
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=13201
Your paranoid android.
=== w2000pro (32 bit) === No test summary line found
=== wxppro (32 bit) === No test summary line found
=== w2003std (32 bit) === No test summary line found
=== wvistau64 (32 bit) === No test summary line found
=== w2008s64 (32 bit) === No test summary line found
=== w7u (32 bit) === No test summary line found
=== w8 (32 bit) === No test summary line found
=== wvistau64 (64 bit) === No test summary line found
=== w2008s64 (64 bit) === No test summary line found