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=126798
Your paranoid android.
=== debian11 (32 bit report) ===
gdiplus: graphicspath.c:1732: Test succeeded inside todo block: Path size 10 does not match expected size 10 graphicspath.c:1732: Test failed: Expected #4: PathPointTypeStart (5.0,10.0) but got PathPointTypeStart (22.5,20.0) graphicspath.c:1732: Test failed: Expected #5: PathPointTypeLine (22.3,0.0) but got PathPointTypeLine (5.0,10.0) graphicspath.c:1732: Test failed: Expected #6: PathPointTypeLine | PathPointTypeCloseSubpath (22.3,20.0) but got PathPointTypeLine | PathPointTypeCloseSubpath (22.5,0.0) graphicspath.c:1732: Test failed: Expected #7: PathPointTypeStart (50.0,10.0) but got PathPointTypeStart (32.5,0.0) graphicspath.c:1732: Test failed: Expected #8: PathPointTypeLine (32.7,20.0) but got PathPointTypeLine (50.0,10.0) graphicspath.c:1732: Test failed: Expected #9: PathPointTypeLine | PathPointTypeCloseSubpath (32.7,0.0) but got PathPointTypeLine | PathPointTypeCloseSubpath (32.5,20.0)
=== debian11 (32 bit zh:CN report) ===
gdiplus: graphicspath.c:1732: Test succeeded inside todo block: Path size 10 does not match expected size 10 graphicspath.c:1732: Test failed: Expected #4: PathPointTypeStart (5.0,10.0) but got PathPointTypeStart (22.5,20.0) graphicspath.c:1732: Test failed: Expected #5: PathPointTypeLine (22.3,0.0) but got PathPointTypeLine (5.0,10.0) graphicspath.c:1732: Test failed: Expected #6: PathPointTypeLine | PathPointTypeCloseSubpath (22.3,20.0) but got PathPointTypeLine | PathPointTypeCloseSubpath (22.5,0.0) graphicspath.c:1732: Test failed: Expected #7: PathPointTypeStart (50.0,10.0) but got PathPointTypeStart (32.5,0.0) graphicspath.c:1732: Test failed: Expected #8: PathPointTypeLine (32.7,20.0) but got PathPointTypeLine (50.0,10.0) graphicspath.c:1732: Test failed: Expected #9: PathPointTypeLine | PathPointTypeCloseSubpath (32.7,0.0) but got PathPointTypeLine | PathPointTypeCloseSubpath (32.5,20.0)
=== debian11b (64 bit WoW report) ===
gdiplus: graphicspath.c:1732: Test succeeded inside todo block: Path size 10 does not match expected size 10 graphicspath.c:1732: Test failed: Expected #4: PathPointTypeStart (5.0,10.0) but got PathPointTypeStart (22.5,20.0) graphicspath.c:1732: Test failed: Expected #5: PathPointTypeLine (22.3,0.0) but got PathPointTypeLine (5.0,10.0) graphicspath.c:1732: Test failed: Expected #6: PathPointTypeLine | PathPointTypeCloseSubpath (22.3,20.0) but got PathPointTypeLine | PathPointTypeCloseSubpath (22.5,0.0) graphicspath.c:1732: Test failed: Expected #7: PathPointTypeStart (50.0,10.0) but got PathPointTypeStart (32.5,0.0) graphicspath.c:1732: Test failed: Expected #8: PathPointTypeLine (32.7,20.0) but got PathPointTypeLine (50.0,10.0) graphicspath.c:1732: Test failed: Expected #9: PathPointTypeLine | PathPointTypeCloseSubpath (32.7,0.0) but got PathPointTypeLine | PathPointTypeCloseSubpath (32.5,20.0)