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=146827
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w7u_el (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w8 (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w864 (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w1064v1507 (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w1064v1809 (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w1064_tsign (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w10pro64 (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w10pro64_en_AE_u8 (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w11pro64 (32 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w7pro64 (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w864 (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w1064v1507 (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w1064v1809 (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w1064_2qxl (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w1064_tsign (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w10pro64 (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w10pro64_ar (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w10pro64_ja (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w10pro64_zh_CN (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')
=== w11pro64_amd (64 bit report) ===
cmd.exe: batch.c:321: Test failed: unexpected char 0x53 position 0 in line 567 (got 'SUCCESS 0', wanted 'FAILURE 1')