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=142447
Your paranoid android.
=== w11pro64 (32 bit report) ===
gdi32: driver.c:214: Test failed: Expect 32. driver.c:231: Test failed: Expect FALSE.1c94:driver: 367 tests executed (0 marked as todo, 0 as flaky, 2 failures), 0 skipped.
Report validation errors: gdi32:driver has no test summary line (early exit of the main process?) gdi32:driver has unaccounted for failure messages
=== w1064_2qxl (64 bit report) ===
gdi32: driver.c:231: Test failed: Expect FALSE.driver.c:231: Test failed: Expect FALSE.1dbc:driver: 400 tests executed (0 marked as todo, 0 as flaky, 2 failures), 0 skipped.
Report validation errors: gdi32:driver has no test summary line (early exit of the main process?) gdi32:driver has unaccounted for failure messages
=== w11pro64_amd (64 bit report) ===
gdi32: driver.c:214: Test failed: Expect 32.