On Fri Jul 8 09:23:33 2022 +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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=118553 Your paranoid android. === w864 (32 bit report) === mf: 04b0:mf: unhandled exception c0000005 at 0042ACE3 === w1064v1507 (32 bit report) === mf: 0da8:mf: unhandled exception c0000005 at 0042ACE3 === w1064v1809 (32 bit report) === mf: 1da0:mf: unhandled exception c0000005 at 0042ACE3 === w1064 (32 bit report) === mf: 1c6c:mf: unhandled exception c0000005 at 0042ACE3 === w1064_tsign (32 bit report) === mf: 0ea4:mf: unhandled exception c0000005 at 0042ACE3 === w10pro64 (32 bit report) === mf: 1e00:mf: unhandled exception c0000005 at 0042ACE3
Hmm, I'll have a look at these in case we're doing some buffer overflow somewhere, but I'm otherwise tempted to only change the test on 64bit. The test change matches what the games are doing.