Julliard, please ignore/reject this patchset, if it wasn't obvious enough how bad it is 😛


On Fri, Mar 29, 2019 at 2:09 PM Marvin <testbot@winehq.org> wrote:
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=50103

Your paranoid android.


=== debian9 (32 bit report) ===

ntoskrnl.exe:
driver.c:799: Test succeeded inside todo block: obj1 != obj2

=== debian9 (32 bit Chinese:China report) ===

ntoskrnl.exe:
driver.c:799: Test succeeded inside todo block: obj1 != obj2

=== debian9 (32 bit WoW report) ===

ntoskrnl.exe:
driver.c:599: Test failed: got 0
driver.c:602: Test failed: got 0x102
driver.c:799: Test succeeded inside todo block: obj1 != obj2

=== debian9 (64 bit WoW report) ===

ntoskrnl.exe:
driver.c:799: Test succeeded inside todo block: obj1 != obj2