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=151181
Your paranoid android.
=== w7u_adm (32 bit report) ===
winmm: midi.c:997: Test failed: bad message 1e/0 from midiStreamOpen, expect 3c7/0 midi.c:1048: Test failed: bad message 3c7/0 from midiStreamOut, expect 3c9/2ff6d8 midi.c:1057: Test failed: bad message 3c9/2ff6d8 from midiStreamClose, expect 3c8/0 midi.c:313: Test failed: bad message 3c8/0 from midiOutOpen, expect 3c7/0 midi.c:372: Test failed: bad message 3c7/0 from midiOutLong unprepared, expect 0/feedf00d
=== w7u_el (32 bit report) ===
winmm: midi.c:997: Test failed: bad message 1e/0 from midiStreamOpen, expect 3c7/0 midi.c:1048: Test failed: bad message 3c7/0 from midiStreamOut, expect 3c9/7bf824 midi.c:1057: Test failed: bad message 3c9/7bf824 from midiStreamClose, expect 3c8/0 midi.c:313: Test failed: bad message 3c8/0 from midiOutOpen, expect 3c7/0 midi.c:372: Test failed: bad message 3c7/0 from midiOutLong unprepared, expect 0/feedf00d
=== debian11b (64 bit WoW report) ===
user32: input.c:4306: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0000000000C100FE, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032