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=120438
Your paranoid android.
=== w1064v1507 (32 bit report) ===
urlmon: url.c:1466: Test failed: progress 65: status = 200
=== w1064v1507 (64 bit report) ===
urlmon: url.c:1466: Test failed: progress 65: status = 200
=== w1064_adm (64 bit report) ===
urlmon: url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200
=== debian11 (32 bit report) ===
urlmon: url.c:1654: Test failed: unexpected call OnProgress_CONNECTING url.c:1466: Test failed: progress 2: status = 302
-
Marvin