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=46489
Your paranoid android.
=== wxppro (32 bit report) ===
crypt32: cert: Timeout
=== w2003std (32 bit report) ===
crypt32: cert: Timeout
=== wvistau64 (32 bit report) ===
crypt32: 0890:cert: unhandled exception c0000005 at 76139B3D
=== wvistau64_zh_CN (32 bit report) ===
crypt32: 0bbc:cert: unhandled exception c0000005 at 75169B3D
=== wvistau64_fr (32 bit report) ===
crypt32: 072c:cert: unhandled exception c0000005 at 75B79B3D
=== wvistau64_he (32 bit report) ===
crypt32: 0bdc:cert: unhandled exception c0000005 at 75AC9B3D
=== w2008s64 (32 bit report) ===
crypt32: 0870:cert: unhandled exception c0000005 at 75809B3D
=== w7u (32 bit report) ===
crypt32: 0ccc:cert: unhandled exception c0000005 at 76189B69
=== w7pro64 (32 bit report) ===
crypt32: 0ad8:cert: unhandled exception c0000005 at 750A9B69
=== w8 (32 bit report) ===
crypt32: 0db4:cert: unhandled exception c0000005 at 77389EAA
=== w8adm (32 bit report) ===
crypt32: 012c:cert: unhandled exception c0000005 at 77389EAA
=== w864 (32 bit report) ===
crypt32: 0a28:cert: unhandled exception c0000005 at 758F9EAA
=== w1064 (32 bit report) ===
crypt32: 0764:cert: unhandled exception c0000005 at 75478658
=== wvistau64 (64 bit report) ===
crypt32: 0890:cert: unhandled exception c0000005 at 000007FEFDA01342
=== w2008s64 (64 bit report) ===
crypt32: 0870:cert: unhandled exception c0000005 at 000007FEFE3A1342
=== w7pro64 (64 bit report) ===
crypt32: 0aec:cert: unhandled exception c0000005 at 000007FEFDEC12B9
=== w864 (64 bit report) ===
crypt32: 074c:cert: unhandled exception c0000005 at 00007FFB25311A31
=== w1064 (64 bit report) ===
crypt32: 0b6c:cert: unhandled exception c0000005 at 00007FFC3B693C60