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=141785
Your paranoid android.
=== debian11 (32 bit report) ===
dinput: driver_bus.c:295: Test failed: id 1: force_feedback.c:4153 got spurious packet driver_bus.c:1103: Test failed: id 1: force_feedback.c:4153 expect[2]: got 0xb000f, expected 0 driver_bus.c:1104: Test failed: id 1: force_feedback.c:4153 expect[2]: got id 1 driver_bus.c:1105: Test failed: id 1: force_feedback.c:4153 expect[2]: got len 2 driver_bus.c:295: Test failed: id 1: force_feedback.c:4218 got spurious packet driver_bus.c:1103: Test failed: id 1: force_feedback.c:4218 expect[2]: got 0xb000f, expected 0 driver_bus.c:1104: Test failed: id 1: force_feedback.c:4218 expect[2]: got id 1 driver_bus.c:1105: Test failed: id 1: force_feedback.c:4218 expect[2]: got len 2 driver_bus.c:295: Test failed: id 1: force_feedback.c:6110 got spurious packet driver_bus.c:1103: Test failed: id 1: force_feedback.c:6110 expect[5]: got 0xb000f, expected 0 driver_bus.c:1104: Test failed: id 1: force_feedback.c:6110 expect[5]: got id 1 driver_bus.c:1105: Test failed: id 1: force_feedback.c:6110 expect[5]: got len 2
=== debian11b (64 bit WoW report) ===
dinput: driver_bus.c:295: Test failed: id 1: force_feedback.c:4153 got spurious packet driver_bus.c:1103: Test failed: id 1: force_feedback.c:4153 expect[2]: got 0xb000f, expected 0 driver_bus.c:1104: Test failed: id 1: force_feedback.c:4153 expect[2]: got id 1 driver_bus.c:1105: Test failed: id 1: force_feedback.c:4153 expect[2]: got len 2 driver_bus.c:295: Test failed: id 1: force_feedback.c:4218 got spurious packet driver_bus.c:1103: Test failed: id 1: force_feedback.c:4218 expect[2]: got 0xb000f, expected 0 driver_bus.c:1104: Test failed: id 1: force_feedback.c:4218 expect[2]: got id 1 driver_bus.c:1105: Test failed: id 1: force_feedback.c:4218 expect[2]: got len 2 driver_bus.c:295: Test failed: id 1: force_feedback.c:6110 got spurious packet driver_bus.c:1103: Test failed: id 1: force_feedback.c:6110 expect[5]: got 0xb000f, expected 0 driver_bus.c:1104: Test failed: id 1: force_feedback.c:6110 expect[5]: got id 1 driver_bus.c:1105: Test failed: id 1: force_feedback.c:6110 expect[5]: got len 2