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=125456
Your paranoid android.
=== debian11 (32 bit report) ===
comctl32: edit.c:3453: Test succeeded inside todo block: Set focus: marked "todo_wine" but succeeds listview.c:2201: Test succeeded inside todo block: Expected 0, got 0 listview.c:2211: Test succeeded inside todo block: Expected 0, got 0 listview.c:2221: Test succeeded inside todo block: Expected 0, got 0 listview.c:2201: Test succeeded inside todo block: Expected 0, got 0 listview.c:2211: Test succeeded inside todo block: Expected 0, got 0 listview.c:2221: Test succeeded inside todo block: Expected 0, got 0 misc.c:969: Test failed: Button 0x7: Expected color 0xff, got 0x808080. misc.c:963: Test succeeded inside todo block: Button 0xa: Expected color 0x808080, got 0x808080.
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000 static.c:116: Test failed: pixel should NOT be painted black! static.c:116: Test failed: pixel should NOT be painted black! win.c:8503: Test failed: GetUpdateRect returned empty region win.c:8504: Test failed: rects do not match (0,0)-(0,0) / (10,10)-(40,40) win.c:8518: Test failed: WM_PAINT should have been received in parent win.c:8562: Test failed: GetUpdateRect returned empty region win.c:8563: Test failed: rects do not match (0,0)-(0,0) / (10,10)-(40,40) win.c:8577: Test failed: WM_PAINT should have been received in parent
=== debian11 (32 bit ar:MA report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (32 bit de report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (32 bit fr report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (32 bit he:IL report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (32 bit hi:IN report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (32 bit ja:JP report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (32 bit zh:CN report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (32 bit WoW report) ===
user32: msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000
=== debian11 (64 bit WoW report) ===
user32: msg.c:19063: Test failed: SendMessage from other thread 1: 1: the msg 0x0400 was expected, but got msg 0x0403 instead msg.c:19063: Test failed: SendMessage from other thread 1: 2: the msg sequence is not complete: expected 0000 - actual 0400 msg.c:19077: Test failed: wrong status 00080000 msg.c:19083: Test failed: SendMessage from other thread 3: 0: the msg 0x0403 was expected, but got msg 0x0401 instead msg.c:19083: Test failed: SendMessage from other thread 3: 1: the msg sequence is not complete: expected 0401 - actual 0000 msg.c:9655: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000