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=52194
Your paranoid android.
=== debian9 (32 bit report) ===
user32: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey:
=== debian9 (32 bit Chinese:China report) ===
user32: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey: msg.c:8713: Test failed: WaitForSingleObject failed 102 msg.c:8719: Test failed: destroy child on thread exit: 0: the msg 0x0082 was expected, but got msg 0x000f instead msg.c:8719: Test failed: destroy child on thread exit: 1: the msg 0x000f was expected, but got msg 0x0014 instead msg.c:8719: Test failed: destroy child on thread exit: 2: the msg sequence is not complete: expected 0014 - actual 0000
=== debian9 (32 bit WoW report) ===
user32: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey:
=== debian9 (64 bit WoW report) ===
user32: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey: monitor.c:110: Test succeeded inside todo block: #0: failed to open registry, error: 0 monitor.c:118: Test failed: #0: wrong DeviceKey: