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=147320
Your paranoid android.
=== w7pro64 (64 bit report) ===
comctl32: 00cc:propsheet: unhandled exception c0000005 at 00000000010C0000
=== w864 (64 bit report) ===
comctl32: 07fc:propsheet: unhandled exception c0000005 at 0000000000830000
=== w1064v1507 (64 bit report) ===
comctl32: 0918:propsheet: unhandled exception c0000005 at 0000000000AD0000
=== w1064v1809 (64 bit report) ===
comctl32: 1f2c:propsheet: unhandled exception c0000005 at 0000000001290000
=== w1064_2qxl (64 bit report) ===
comctl32: 0430:propsheet: unhandled exception c0000005 at 0000000000380000
=== w1064_adm (64 bit report) ===
comctl32: 1de8:propsheet: unhandled exception c0000005 at 00000000000D0000
=== w1064_tsign (64 bit report) ===
comctl32: 1e6c:propsheet: unhandled exception c0000005 at 0000000000DE0000
=== w10pro64 (64 bit report) ===
comctl32: 1e7c:propsheet: unhandled exception c0000005 at 00000000008F0000
=== w10pro64_ar (64 bit report) ===
comctl32: 2238:propsheet: unhandled exception c0000005 at 0000000000660000
=== w10pro64_ja (64 bit report) ===
comctl32: 1530:propsheet: unhandled exception c0000005 at 0000000000870000
=== w10pro64_zh_CN (64 bit report) ===
comctl32: 0e88:propsheet: unhandled exception c0000005 at 0000000000FA0000
=== w11pro64_amd (64 bit report) ===
comctl32: 1458:propsheet: unhandled exception c0000005 at 00000000005A0000
=== debian11b (64 bit WoW report) ===
Report validation errors: comctl32:propsheet crashed (c0000005)