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=45850
Your paranoid android.
=== wxppro (32 bit report) ===
gdiplus: 0b40:font: unhandled exception c0000005 at 00000000
=== w2003std (32 bit report) ===
gdiplus: 06ac:font: unhandled exception c0000005 at 00000000
=== wvistau64 (32 bit report) ===
gdiplus: 0370:font: unhandled exception c0000005 at 006F0130
=== wvistau64_zh_CN (32 bit report) ===
gdiplus: 0bbc:font: unhandled exception c0000005 at 029F0130
=== wvistau64_fr (32 bit report) ===
gdiplus: 072c:font: unhandled exception c0000005 at 02BC0130
=== wvistau64_he (32 bit report) ===
gdiplus: 0bd8:font: unhandled exception c0000005 at 00E40130
=== w2008s64 (32 bit report) ===
gdiplus: 0870:font: unhandled exception c0000005 at 00C30130
=== w7u (32 bit report) ===
gdiplus: 0b70:font: unhandled exception c0000005 at 71856076
=== w7pro64 (32 bit report) ===
gdiplus: 0ad8:font: unhandled exception c0000005 at 31005927
=== w8 (32 bit report) ===
gdiplus: 0dd8:font: unhandled exception c0000005 at 00000000
=== w8adm (32 bit report) ===
gdiplus: 0ff0:font: unhandled exception c0000005 at 00000000
=== w864 (32 bit report) ===
gdiplus: 0ac8:font: unhandled exception c0000005 at 00000000
=== w1064 (32 bit report) ===
gdiplus: 085c:font: unhandled exception c0000005 at 00000000
=== wvistau64 (64 bit report) ===
gdiplus: 0890:font: unhandled exception c0000005 at 00000000022701F8
=== w2008s64 (64 bit report) ===
gdiplus: 0870:font: unhandled exception c0000005 at 00000000024F01F8
=== w7pro64 (64 bit report) ===
gdiplus: 0adc:font: unhandled exception c0000005 at 000007FEFB69AF1A
=== w864 (64 bit report) ===
gdiplus: 0a20:font: unhandled exception c0000005 at 0000000000000000
=== w1064 (64 bit report) ===
gdiplus: 0c3c:font: unhandled exception c0000005 at 0000000000000000