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=18547
Your paranoid android.
=== WNT4WSSP6 (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
=== TEST64_W7SP1 (32 bit) === No test summary line found
=== W7PROX64 (64 bit) === No test summary line found
=== TEST64_W7SP1 (64 bit) === No test summary line found
On Wed, 23 May 2012, 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=18547
I believe this is the usual VBScript test issue. At least the test passed on my Windows XP VM.