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=137104
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
dwrite: 0394:analyzer: unhandled exception c0000005 at 71D1903F
=== w7u_adm (32 bit report) ===
dwrite: 0878:analyzer: unhandled exception c0000005 at 6EDA903F
=== w7u_el (32 bit report) ===
dwrite: 0a64:analyzer: unhandled exception c0000005 at 723C903F
=== w8 (32 bit report) ===
dwrite: 0bfc:analyzer: unhandled exception c0000005 at 72BD9878
=== w8adm (32 bit report) ===
dwrite: 0ad0:analyzer: unhandled exception c0000005 at 72919878
=== w864 (32 bit report) ===
dwrite: 0b64:analyzer: unhandled exception c0000005 at 72A99878
=== w1064v1507 (32 bit report) ===
dwrite: 0cac:analyzer: unhandled exception c0000005 at 73ED5C23
=== w1064v1809 (32 bit report) ===
dwrite: 1e3c:analyzer: unhandled exception c0000005 at 74D22499
=== w1064_tsign (32 bit report) ===
dwrite: 1eac:analyzer: unhandled exception c0000005 at 75636181
=== w10pro64 (32 bit report) ===
dwrite: 1f78:analyzer: unhandled exception c0000005 at 73CE6181
=== w11pro64 (32 bit report) ===
dwrite: 06e4:analyzer: unhandled exception c0000005 at 745217A8
=== w7pro64 (64 bit report) ===
dwrite: 0be0:analyzer: unhandled exception c0000005 at 000007FEF465827A
=== w864 (64 bit report) ===
dwrite: 0b70:analyzer: unhandled exception c0000005 at 00007FFA44F9278C
=== w1064v1507 (64 bit report) ===
dwrite: 0ca0:analyzer: unhandled exception c0000005 at 00007FFD56907FBC
=== w1064v1809 (64 bit report) ===
dwrite: 1c88:analyzer: unhandled exception c0000005 at 00007FFB6BA356BE
=== w1064_2qxl (64 bit report) ===
dwrite: 1cf4:analyzer: unhandled exception c0000005 at 00007FF8A9E6CCDE
=== w1064_adm (64 bit report) ===
dwrite: 1cc4:analyzer: unhandled exception c0000005 at 00007FFF94CECCDE
=== w1064_tsign (64 bit report) ===
dwrite: 1e2c:analyzer: unhandled exception c0000005 at 00007FF951ADCCDE
=== w10pro64 (64 bit report) ===
dwrite: 20bc:analyzer: unhandled exception c0000005 at 00007FFF1E5FCCDE
=== w10pro64_en_AE_u8 (64 bit report) ===
dwrite: 2204:analyzer: unhandled exception c0000005 at 00007FFA648FCCDE
=== w10pro64_ar (64 bit report) ===
dwrite: 2190:analyzer: unhandled exception c0000005 at 00007FF9F8FBCCDE
=== w10pro64_ja (64 bit report) ===
dwrite: 226c:analyzer: unhandled exception c0000005 at 00007FF9609CCCDE
=== w10pro64_zh_CN (64 bit report) ===
dwrite: 09cc:analyzer: unhandled exception c0000005 at 00007FF8A77DCCDE
=== w11pro64_amd (64 bit report) ===
dwrite: 1924:analyzer: unhandled exception c0000005 at 00007FFE98C50414