On 6/18/21 2:46 PM, 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=92750
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
ntoskrnl.exe: ntoskrnl.c:2621: Test failed: report 0: WriteFile failed, last error 87 ntoskrnl.c:2622: Test failed: report 0: WriteFile returned 0 ntoskrnl.c:2628: Test failed: report 0: ReadFile failed, last error 1167 ntoskrnl.c:2629: Test failed: report 0: ReadFile returned 0 ntoskrnl.c:2630: Test failed: report 0: unexpected report data
=== w7u_el (32 bit report) ===
ntoskrnl.exe: driver.c:759: Test failed: got 0 ntoskrnl.c:2621: Test failed: report 0: WriteFile failed, last error 87 ntoskrnl.c:2622: Test failed: report 0: WriteFile returned 0 ntoskrnl: Timeout
=== w1064_tsign (64 bit report) ===
ntoskrnl.exe: driver.c:272: Test failed: Got unexpected test_load_image_notify_count 0.
I incorrectly considered W10 behavior to be standard, and it looks like older versions didn't check the report IDs on write, so I'll have to fix these last two patches.