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=135234
Your paranoid android.
=== w864 (32 bit report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== w1064v1507 (32 bit report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== w1064v1809 (32 bit report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== w11pro64 (32 bit report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== debian11 (32 bit ar:MA report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== debian11 (32 bit fr report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== debian11 (32 bit he:IL report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== debian11 (32 bit hi:IN report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== debian11 (32 bit ja:JP report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc
=== debian11 (32 bit zh:CN report) ===
kernel32: heap.c:3295: Test failed: got 0xbacccccc heap.c:3295: Test failed: got 0xbacccccc