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=143376
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
taskschd: 0558:scheduler: unhandled exception c0000005 at 000E8F30
=== w7u_el (32 bit report) ===
taskschd: 0a6c:scheduler: unhandled exception c0000005 at 00508F30
=== w8 (32 bit report) ===
taskschd: 0bbc:scheduler: unhandled exception c0000002 at 754C1A3A
=== w8adm (32 bit report) ===
taskschd: 0a6c:scheduler: unhandled exception c0000002 at 75461A3A
=== w864 (32 bit report) ===
taskschd: 02d0:scheduler: unhandled exception c0000002 at 75454128
=== w1064v1507 (32 bit report) ===
taskschd: 0394:scheduler: unhandled exception c0000005 at 01646F98
=== w1064v1809 (32 bit report) ===
taskschd: 1ddc:scheduler: unhandled exception c0000005 at 00EF3EF8
=== w1064_tsign (32 bit report) ===
taskschd: 0e90:scheduler: unhandled exception c0000005 at 01525530
=== w10pro64 (32 bit report) ===
taskschd: 2118:scheduler: unhandled exception c0000005 at 00D427A0
=== w10pro64_en_AE_u8 (32 bit report) ===
taskschd: 0bc4:scheduler: unhandled exception c0000005 at 00DF6E08
=== w11pro64 (32 bit report) ===
taskschd: 008c:scheduler: unhandled exception c0000002 at 769207B2
=== w7pro64 (64 bit report) ===
taskschd: 06f0:scheduler: unhandled exception c0000005 at 000000000090AD40
=== w864 (64 bit report) ===
taskschd: 0b68:scheduler: unhandled exception c0000005 at 000000000072B220
=== w1064v1507 (64 bit report) ===
taskschd: 0f10:scheduler: unhandled exception c0000002 at 00007FFADB3AA1C8
=== w1064v1809 (64 bit report) ===
taskschd: 1dd8:scheduler: unhandled exception c0000005 at 00000000007FAA60
=== w1064_2qxl (64 bit report) ===
taskschd: 1e30:scheduler: unhandled exception c0000002 at 00007FFFFB10CD29
=== w1064_adm (64 bit report) ===
taskschd: 1ca8:scheduler: unhandled exception c0000005 at 0000000000C7A430
=== w1064_tsign (64 bit report) ===
taskschd: 11c0:scheduler: unhandled exception c0000002 at 00007FF903B4CD29
=== w10pro64 (64 bit report) ===
taskschd: 206c:scheduler: unhandled exception c0000002 at 00007FFF2C874F69
=== w10pro64_ar (64 bit report) ===
taskschd: 2104:scheduler: unhandled exception c0000002 at 00007FFA072F4F69
=== w10pro64_ja (64 bit report) ===
taskschd: 23d4:scheduler: unhandled exception c0000002 at 00007FF96EAF4F69
=== w10pro64_zh_CN (64 bit report) ===
taskschd: 234c:scheduler: unhandled exception c0000002 at 00007FF8B5764F69
=== w11pro64_amd (64 bit report) ===
taskschd: 1af0:scheduler: unhandled exception c0000002 at 00007FFBEDFF428C