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=143187
Your paranoid android.
=== w10pro64_en_AE_u8 (32 bit report) ===
kernel32: heap.c:3314: Test failed: HeapValidate failed heap.c:3323: Test failed: HeapValidate failed
=== w10pro64 (32 bit report) ===
kernel32: loader.c:3150: Test failed: attached thread count should be 2 loader.c:3361: Test failed: expected thread exit code 196, got 259 loader.c:3361: Test failed: expected thread exit code 196, got 259 loader.c:2854: Test failed: expected thread exit code 196, got 195 loader.c:2854: Test failed: expected thread exit code 196, got 195
=== w1064_adm (64 bit report) ===
kernel32: loader.c:713: Test failed: 1415: wrong status c000007b/0 loader.c:718: Test failed: 1415: failed with c000007b expected fallback loader.c:713: Test failed: 1421: wrong status c000007b/0 loader.c:718: Test failed: 1421: failed with c000007b expected fallback