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=1828
Your paranoid android.
=== W98SE (32 bit) === No test summary line found
=== W2KPROSP4 (32 bit) === No test summary line found
=== WXPPROSP3 (32 bit) === No test summary line found
=== W2K3R2SESP2 (32 bit) === No test summary line found
=== WVISTAADM (32 bit) === No test summary line found
=== W2K8SE (32 bit) === No test summary line found
=== W7PRO (32 bit) === No test summary line found
=== W7PROX64 (32 bit) === No test summary line found
=== W7PROX64 (64 bit) === No test summary line found
On 04/29/2010 06:54 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 http://testbot.winehq.org/JobDetails.pl?Key=1828
Your paranoid android.
=== W98SE (32 bit) === No test summary line found
=== W2KPROSP4 (32 bit) === No test summary line found
=== WXPPROSP3 (32 bit) === No test summary line found
=== W2K3R2SESP2 (32 bit) === No test summary line found
=== WVISTAADM (32 bit) === No test summary line found
=== W2K8SE (32 bit) === No test summary line found
=== W7PRO (32 bit) === No test summary line found
=== W7PROX64 (32 bit) === No test summary line found
=== W7PROX64 (64 bit) === No test summary line found
They all show:
mshtml: start - - Usage: C:\winetest\mshtml_test.exe test_name
Valid test names: dom events htmldoc htmllocation misc protocol script mshtml: done (1)
The only file changed in this patch is jstest.html but that one doesn't have a corresponding test executable. If jstest.html changes, the testbot should actually run the script test.