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=145248
Your paranoid android.
=== w10pro64_zh_CN (64 bit report) ===
msvcr80: msvcr80.c:290: Test failed: Binary buffer mismatch - expected b0 00 cc , got b0 b1 00 msvcr80.c:295: Test failed: Binary buffer mismatch - expected b0 b1 00 cc , got b0 b1 b2 b3 msvcr80.c:300: Test failed: Binary buffer mismatch - expected b0 00 cc , got 00 b1 cc msvcr80.c:72: Test failed: unexpected call invalid_parameter_handler msvcr80.c:304: Test failed: got 34. msvcr80.c:305: Test failed: Binary buffer mismatch - expected b0 00 cc , got 00 cc cc msvcr80.c:312: Test failed: Binary buffer mismatch - expected 00 b1 cc , got 00 cc cc
=== debian11 (32 bit zh:CN report) ===
msvcr80: msvcr80.c:290: Test failed: Binary buffer mismatch - expected b0 00 cc , got b0 b1 00 msvcr80.c:295: Test failed: Binary buffer mismatch - expected b0 b1 00 cc , got b0 b1 b2 b3 msvcr80.c:72: Test failed: unexpected call invalid_parameter_handler msvcr80.c:304: Test failed: got 34. msvcr80.c:305: Test failed: Binary buffer mismatch - expected b0 00 cc , got 00 b1 cc