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=70403 Your paranoid android. === w1064v1809_ar (32 bit report) === kernel32: loader.c:3215: Test failed: child process failed to terminate === w1064v1809_he (32 bit report) === kernel32: loader.c:3215: Test failed: child process failed to terminate === w1064v1809_ja (32 bit report) === kernel32: loader.c:3215: Test failed: child process failed to terminate === w1064v1809_zh_CN (32 bit report) === kernel32: loader.c:3187: Test failed: child process failed to terminate === w864 (64 bit report) === kernel32: loader.c:696: Test failed: 1172: wrong status c0000130/c000007b loader.c:696: Test failed: 1177: wrong status c0000130/c000007b === w1064v1809 (64 bit report) === kernel32: loader.c:692: Test failed: 1392: got test dll but expected fallback loader.c:692: Test failed: 1398: got test dll but expected fallback loader.c:692: Test failed: 1404: got test dll but expected fallback loader.c:692: Test failed: 1411: got test dll but expected fallback loader.c:692: Test failed: 1438: got test dll but expected fallback === w1064v1809 (32 bit report) === ntdll: 1808:rtl: unhandled exception c0000005 at 77D89D4B === w1064v1809_2scr (32 bit report) === ntdll: 195c:rtl: unhandled exception c0000005 at 77BA9D4B === w1064v1809_ar (32 bit report) === ntdll: 06f4:rtl: unhandled exception c0000005 at 77219D4B === w1064v1809_he (32 bit report) === ntdll: 0e64:rtl: unhandled exception c0000005 at 77D39D4B === w1064v1809_ja (32 bit report) === ntdll: 19b8:rtl: unhandled exception c0000005 at 772B9D4B === w1064v1809_zh_CN (32 bit report) === ntdll: 1854:rtl: unhandled exception c0000005 at 77979D4B === debiant (build log) === The task timed out === debiant (build log) === The task timed out