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=124925
Your paranoid android.
=== w7u_2qxl (testbot log) ===
Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 6.
=== w7u_adm (testbot log) ===
Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 6.
=== w7u_el (testbot log) ===
Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 6.
=== w1064v1507 (32 bit report) ===
windows.devices.enumeration: 056c:devices: unhandled exception c0000005 at 74106FE9
=== w10pro64_en_AE_u8 (64 bit report) ===
windows.devices.enumeration: 1ce4:devices: unhandled exception c0000005 at 00007FF98BF344E7
=== w10pro64_ar (64 bit report) ===
windows.devices.enumeration: 0f80:devices: unhandled exception c0000005 at 00007FFC40CC44E7
=== w10pro64_ja (64 bit report) ===
windows.devices.enumeration: 1160:devices: unhandled exception c0000005 at 0000000000000000
=== w10pro64_zh_CN (64 bit report) ===
windows.devices.enumeration: 2050:devices: unhandled exception c0000005 at 00007FFD2AB344E7
=== debian11 (build log) ===
Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24707. Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24707. Use of uninitialized value $Flaky in addition (+) at /home/testbot/lib/WineTestBot/LogUtils.pm line 720, <$LogFile> line 24707.