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=87294
Your paranoid android.
=== w1064v1809 (32 bit report) ===
windows.gaming.input: 12e0:input: unhandled exception c0000005 at 7370C22E
=== w1064 (32 bit report) ===
windows.gaming.input: 1c34:input: unhandled exception c0000005 at 7480C523
=== w10pro64 (32 bit report) ===
windows.gaming.input: 0608:input: unhandled exception c0000005 at 7521C523
=== w1064v1809 (64 bit report) ===
windows.gaming.input: 1608:input: unhandled exception c0000005 at 00007FFFAF26653F
=== w1064 (64 bit report) ===
windows.gaming.input: 1ae8:input: unhandled exception c0000005 at 00007FFDDCCC6A7B
=== w1064_2qxl (64 bit report) ===
windows.gaming.input: 1aa0:input: unhandled exception c0000005 at 00007FFACDCE6A7B
=== w10pro64 (64 bit report) ===
windows.gaming.input: 09c4:input: unhandled exception c0000005 at 00007FFEE8BC6A7B
=== w10pro64_ar (64 bit report) ===
windows.gaming.input: 14fc:input: unhandled exception c0000005 at 00007FFB7E706A7B
=== w10pro64_he (64 bit report) ===
windows.gaming.input: 1c9c:input: unhandled exception c0000005 at 00007FFACE396A7B
=== w10pro64_ja (64 bit report) ===
windows.gaming.input: 1e20:input: unhandled exception c0000005 at 00007FFC0F6D6A7B
=== w10pro64_zh_CN (64 bit report) ===
windows.gaming.input: 1ef8:input: unhandled exception c0000005 at 00007FFA36846A7B