On Sun Jan 8 19:44:59 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 full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=128223 Your paranoid android. === w7u_2qxl (32 bit report) === ntoskrnl.exe: driver.c:2321: Test failed: got 8491F9A8 != 00000000 === w7u_el (32 bit report) === ntoskrnl.exe: driver.c:2321: Test failed: got 84A21620 != 00000000 === w8 (32 bit report) === ntoskrnl.exe: driver.c:2321: Test failed: got 8A0469F8 != 00000000 === w1064_tsign (64 bit report) === ntoskrnl.exe: driver.c:2321: Test failed: got FFFFDD82EB0DCC30 != 0000000000000000
so the test with STATUS_OBJECT_NAME_COLLISION causes it to set the value to NULL, very interesting