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=9486
Your paranoid android.
=== WNT4WSSP6 (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== W2KPROSP4 (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== WXPPROSP3 (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== W2K3R2SESP2 (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== WVISTAADM (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== W2K8SE (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== W7PRO (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== W7PROX64 (32 bit status) === status.c:412: Test failed: Expected 1, got 0
=== W7PROX64 (64 bit status) === status.c:412: Test failed: Expected 1, got 0
On 26/02/11 04:12, Marvin wrote:
http://testbot.winehq.org/JobDetails.pl?Key=9486
=== W7PROX64 (64 bit status) === status.c:412: Test failed: Expected 1, got 0
Please ignore all 3 patches in the set. I will investigate Win behaviour a little closer and resubmit the patches once I learn more.