On 2/13/23 23:14, Marvin wrote:
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=129371
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
ntoskrnl.exe: ntoskrnl.c:1505: Test failed: wrong class {00000000-0000-0000-0000-000000000000} ntoskrnl.c:1513: Test failed: wrong class {00000000-0000-0000-0000-000000000000} ntoskrnl.c:1515: Test failed: got flags 0 ntoskrnl.c:1519: Test failed: failed to get interface path, error 0x57 ntoskrnl.c:1520: Test failed: wrong path "x\x19)" ntoskrnl.c:1526: Test failed: got error 123
I'm not sure what went wrong here. Possibly a race condition—the driver wasn't actually loaded in time? Either way it shouldn't be related to this patch series.
=== w1064_tsign (64 bit report) ===
ntoskrnl.exe: ntoskrnl.c:1219: Test failed: Got unexpected ret -1. ntoskrnl.c:1220: Test failed: Received unexpected data.
Not quite clear what went wrong here, but it shouldn't be related either.