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=150884
Your paranoid android.
=== w8 (32 bit report) ===
windows.web: web.c:229: Test failed: got hr 0x8007000e.
=== w8adm (32 bit report) ===
windows.web: 0a98:web: unhandled exception c0000005 at 77B89925
=== w864 (32 bit report) ===
windows.web: web: Timeout
=== w1064v1809 (32 bit report) ===
windows.web: web.c:229: Test failed: got hr 0x8007000e. 1dd8:web: unhandled exception c0000005 at 77AB7962
=== w1064_tsign (32 bit report) ===
windows.web: 1cd8:web: unhandled exception c0000005 at 77334626
=== w10pro64 (32 bit report) ===
windows.web: web.c:229: Test failed: got hr 0x8007000e. web.c:229: Test failed: got hr 0x8007000e. web.c:352: Test failed: got hr 0x8007000e. web.c:358: Test failed: got hr 0x8007000e.
=== w10pro64_en_AE_u8 (32 bit report) ===
windows.web: 2360:web: unhandled exception c0000005 at 77B08491
=== w11pro64 (32 bit report) ===
windows.web: web.c:229: Test failed: got hr 0x8007000e. 0464:web: unhandled exception c0000005 at 77BB7061
=== debian11b (64 bit WoW report) ===
Report validation errors: d3d11:d3d11 has no test summary line (early exit of the main process?) d3d11:d3d11 has unaccounted for failure messages d3d11:d3d11 has unaccounted for todo messages d3d11:d3d11 has unaccounted for skip messages