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=73637
Your paranoid android.
=== w1064v1809_he (32 bit report) ===
kernel32: loader.c:3249: Test failed: child process failed to terminate
=== w1064v1809_ja (32 bit report) ===
kernel32: loader.c:3221: Test failed: child process failed to terminate
=== w1064v1809_zh_CN (32 bit report) ===
kernel32: loader.c:3249: Test failed: child process failed to terminate
=== w1064v1809 (64 bit report) ===
kernel32: loader.c:704: Test failed: 1426: got test dll but expected fallback loader.c:704: Test failed: 1432: got test dll but expected fallback loader.c:704: Test failed: 1438: got test dll but expected fallback loader.c:704: Test failed: 1445: got test dll but expected fallback loader.c:704: Test failed: 1472: got test dll but expected fallback
=== debiant (build log) ===
/usr/bin/i686-w64-mingw32-ld: dbghelp.cross.o:dbghelp.c:(.data+0x1c): undefined reference to `cpu_ppc' collect2: error: ld returned 1 exit status Task: The win32 Wine build failed
=== debiant (build log) ===
/usr/bin/x86_64-w64-mingw32-ld: dbghelp.cross.o:dbghelp.c:(.data+0x30): undefined reference to `cpu_ppc' collect2: error: ld returned 1 exit status Task: The wow64 Wine build failed