ntdll:info is a flaky test marked todo_wine that succeeds sometimes: "info.c:822: Test succeeded inside todo block: Expected to read 0 bytes, got 0"
Hardy seems to be the common variable for failures, and it seems as though an actual failure reading from location 0x1234 is the trigger. (The historically normal case, apparently, is that we succeed in doing the read).
git-blame points at Peter as the last to touch this. I've attached a potential patch, hopefully it'll be wrong and force Peter to step up and fix it correctly <grin>.
Cheers,
Jeremy
diff --git a/dlls/ntdll/tests/info.c b/dlls/ntdll/tests/info.c index 9fab806..140be05 100644 --- a/dlls/ntdll/tests/info.c +++ b/dlls/ntdll/tests/info.c @@ -819,7 +819,8 @@ static void test_readvirtualmemory(void) todo_wine{ status = pNtReadVirtualMemory(process, (void *) 0x1234, buffer, 12, &readcount); ok( status == STATUS_PARTIAL_COPY, "Expected STATUS_PARTIAL_COPY, got %08x\n", status); - ok( readcount == 0, "Expected to read 0 bytes, got %ld\n",readcount); + if (status == STATUS_PARTIAL_COPY) + ok( readcount == 0, "Expected to read 0 bytes, got %ld\n",readcount); }
/* 0 handle */