On Wed May 24 14:09:43 2023 +0000, **** wrote:
Marvin replied on the mailing list:
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=133007 Your paranoid android. === w7u_adm (32 bit report) === kernel32: actctx.c:3971: Test failed: tests[28] (00000002 0x0000): expected error 14001, got 0
Re-run the test, and it says:
``` actctx.c:3971: Test failed: tests[26] (00000002 0x007f): expected error 14001, got 0 actctx.c:3971: Test failed: tests[28] (00000002 0x0000): expected error 14001, got 0 ```