Hi,
It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=127424
Your paranoid android.
=== w1064v1507 (32 bit report) ===
setupapi: 0da4:misc: unhandled exception c0000005 at 76D38FEB
=== w1064v1809 (32 bit report) ===
setupapi: 1c74:misc: unhandled exception c0000005 at 76A0DCEB
=== w1064_tsign (32 bit report) ===
setupapi: 0410:misc: unhandled exception c0000005 at 769184FB
=== w10pro64 (32 bit report) ===
setupapi: 1e74:misc: unhandled exception c0000005 at 771192EB
=== w1064v1507 (64 bit report) ===
setupapi: 0cd0:misc: unhandled exception c0000005 at 00007FF9248112A0
=== w1064v1809 (64 bit report) ===
setupapi: 1c8c:misc: unhandled exception c0000005 at 00007FFAC336A870
=== w1064_2qxl (64 bit report) ===
setupapi: 1c10:misc: unhandled exception c0000005 at 00007FF8E9EB16A0
=== w1064_adm (64 bit report) ===
setupapi: 1878:misc: unhandled exception c0000005 at 00007FFFA67E16A0
=== w1064_tsign (64 bit report) ===
setupapi: 0620:misc: unhandled exception c0000005 at 00007FFA0F0416A0
=== w10pro64 (64 bit report) ===
setupapi: 1e88:misc: unhandled exception c0000005 at 00007FFCF27F16A0
=== w10pro64_en_AE_u8 (64 bit report) ===
setupapi: 2394:misc: unhandled exception c0000005 at 00007FF99C8016A0
=== w10pro64_ar (64 bit report) ===
setupapi: 22d8:misc: unhandled exception c0000005 at 00007FFC519416A0
=== w10pro64_ja (64 bit report) ===
setupapi: 234c:misc: unhandled exception c0000005 at 00007FFA427116A0
=== w10pro64_zh_CN (64 bit report) ===
setupapi: 1774:misc: unhandled exception c0000005 at 00007FFD3B1816A0