On 4/9/21 12:28 AM, Marvin wrote:
Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=88497
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
ntoskrnl.exe: ntoskrnl.c:1109: Test failed: failed to get device, error 0x103 ntoskrnl.c:1166: Test failed: failed to open child: 0xc000000e ntoskrnl.c:1170: Test failed: got error 6 ntoskrnl.c:1171: Test failed: got id -559038737 ntoskrnl.c:1172: Test failed: got size 0 ntoskrnl.c:1321: Test failed: expected failure ntoskrnl.c:1322: Test failed: got error 0 ntoskrnl.c:290: Test failed: expected SERVICE_STOPPED, got 0 ntoskrnl.c:1350: Test failed: Failed to uninstall INF, error 3758096957
=== w7u_el (32 bit report) ===
ntoskrnl.exe: driver.c:1263: Test failed: Type = 134 ntoskrnl.c:1109: Test failed: failed to get device, error 0x103 ntoskrnl.c:1166: Test failed: failed to open child: 0xc000000e ntoskrnl.c:1170: Test failed: got error 6 ntoskrnl.c:1171: Test failed: got id -559038737 ntoskrnl.c:1172: Test failed: got size 0
Evidently IoInvalidateDeviceRelations() is asynchronous on Windows, and was just always fast enough on my test VM to never hit this case. I'll add some explicit synchronization.