Hi,
While running your changed tests, 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=65515
Your paranoid android.
=== w864 (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1507 (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1809 (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87) registry.c:3424: Test failed: expected ERROR_SUCCESS, got 6 registry.c:3552: Test failed: expected WAIT_OBJECT_0, got 258
=== w1064v1809_2scr (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1809_ar (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1809_he (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1809_ja (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1809_zh_CN (32 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w864 (64 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1507 (64 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)
=== w1064v1809 (64 bit report) ===
advapi32: registry.c:1100: Test failed: RegOpenKeyEx with KEY_WOW64_64KEY failed (err=87)