- wine-devel - winehq.org

Re: [PATCH v2 7/7] dinput/tests: Test GetObjectInfo() with three sliders and a proper format.
by Marvin 25 Jul '22

25 Jul '22

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=119555 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v2 6/7] dinput/tests: Assert that we can't get info about the third slider with c_dfDIJoystick2.
by Marvin 25 Jul '22

25 Jul '22

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=119554 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x500: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v2 5/7] dinput: Use GUID_Slider type for dials.
by Marvin 25 Jul '22

25 Jul '22

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=119553 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v2 3/7] dinput/tests: Use helper for checking device object instances.
by Marvin 25 Jul '22

25 Jul '22

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=119551 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x500: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v4 2/2] mfplat/tests: Merge and reorganize image format tests.
by Marvin 25 Jul '22

25 Jul '22

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=119548 Your paranoid android. === w7u_2qxl (32 bit report) === mfplat: 0124:mfplat: unhandled exception c0000005 at 6ECF7D1C === w7u_el (32 bit report) === mfplat: 085c:mfplat: unhandled exception c0000005 at 72297D1C

1 0

Re: [PATCH v4 1/2] mfplat/tests: Mark some tests as broken on Win 8 and 10 v1507.
by Marvin 25 Jul '22

25 Jul '22

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=119547 Your paranoid android. === w7u_adm (32 bit report) === mfplat: 0884:mfplat: unhandled exception c0000005 at 6EFB7D1C

1 0

Re: [PATCH v2 09/10] mshtml: Implement ProgressEvent's total prop.
by Marvin 23 Jul '22

23 Jul '22

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=119500 Your paranoid android. === w10pro64_ja (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Testbot outage
by Jeremy White 23 Jul '22

23 Jul '22

Hi all, We are moving offices. As a result, the WineHQ testnet that powers testbot will be unavailable for some time, starting at 1:30 CDT. It will hopefully just be for the afternoon. Cheers, Jeremy

3 2

Re: [PATCH v2 07/10] mshtml: Implement ProgressEvent's lengthComputable prop.
by Marvin 22 Jul '22

22 Jul '22

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=119498 Your paranoid android. === w1064v1507 (64 bit report) === mshtml: events: Timeout

1 0

Re: [PATCH v2 1/8] dlls/msvcrt: improve support for template in methods
by Marvin 22 Jul '22

22 Jul '22

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=119463 Your paranoid android. === debian11 (32 bit report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Arabic:Morocco report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit German report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit French report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Hebrew:Israel report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Hindi:India report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Japanese:Japan report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Chinese:China report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit WoW report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (64 bit WoW report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64"

1 0

Re: [PATCH 2/8] dinput/test: Print the expected values in check_ macros.
by Marvin 22 Jul '22

22 Jul '22

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=119447 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1836: Test failed: 0x700: state[0]: WaitForSingleObject succeeded === w1064_tsign (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 2/3] shell32: Add SHBindToFolderIDListParent tests.
by Marvin 22 Jul '22

22 Jul '22

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=119429 Your paranoid android. === w1064_2qxl (64 bit report) === shell32: shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064_adm (64 bit report) === shell32: shlfolder.c:4992: Test failed: MKDIR: expected notification type 8, got: 40000 === w1064_tsign (64 bit report) === shell32: shlfolder.c:5009: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === debian11 (32 bit report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Arabic:Morocco report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit German report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit French report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Hebrew:Israel report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Hindi:India report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Japanese:Japan report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Chinese:China report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (64 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got 00000000DEADBEEF

1 0

Re: [PATCH 8/8] dinput/tests: Test GetObjectInfo() with three sliders and a proper format.
by Marvin 22 Jul '22

22 Jul '22

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=119453 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1836: Test failed: 0x500: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH 4/8] dinputs/tests: Use helper for checking device object instances.
by Marvin 22 Jul '22

22 Jul '22

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=119449 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1836: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH 3/4] ws2_32: Map AFD_POLL_RESET to both POLLHUP and POLLERR.
by Marvin 22 Jul '22

22 Jul '22

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=119426 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit German report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit French report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit WoW report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (64 bit WoW report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12

1 0

Re: [PATCH v2 6/9] win32u/tests: Add tests for catching exceptions from timer proc.
by Marvin 22 Jul '22

22 Jul '22

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=119391 Your paranoid android. === build (build log) === error: patch failed: dlls/user32/message.c:856 error: patch failed: dlls/user32/user_private.h:89 error: patch failed: dlls/user32/winproc.c:719 error: patch failed: dlls/win32u/message.c:2952 error: patch failed: include/ntuser.h:276 error: patch failed: dlls/user32/message.c:877 error: patch failed: dlls/win32u/message.c:2496 error: patch failed: dlls/win32u/sysparams.c:4880 error: patch failed: dlls/win32u/win32u_private.h:436 error: patch failed: include/ntuser.h:902 error: patch failed: dlls/user32/message.c:597 error: patch failed: dlls/win32u/hook.c:60 error: patch failed: dlls/win32u/message.c:109 error: patch failed: dlls/win32u/tests/win32u.c:425 error: patch failed: dlls/win32u/win32u_private.h:391 error: patch failed: dlls/ntdll/signal_arm.c:533 error: patch failed: dlls/ntdll/signal_arm64.c:576 error: patch failed: dlls/ntdll/signal_i386.c:257 error: patch failed: dlls/ntdll/signal_x86_64.c:661 error: patch failed: dlls/ntdll/unix/signal_arm.c:721 error: patch failed: dlls/ntdll/unix/signal_arm64.c:730 error: patch failed: dlls/ntdll/unix/signal_i386.c:1575 error: patch failed: dlls/ntdll/unix/signal_x86_64.c:2327 error: patch failed: dlls/win32u/gdiobj.c:1158 error: patch failed: dlls/win32u/message.c:2514 error: patch failed: dlls/win32u/syscall.c:117 error: patch failed: dlls/win32u/win32u.spec:839 error: patch failed: dlls/win32u/win32u_private.h:215 error: patch failed: dlls/win32u/wrappers.c:855 error: patch failed: dlls/wow64win/syscall.h:104 error: patch failed: dlls/wow64win/user.c:78 error: patch failed: dlls/win32u/tests/win32u.c:632 Task: Patch failed to apply

1 0

Re: [PATCH v2 3/9] win32u: Avoid using client callbacks for NtUserSendMessage.
by Marvin 22 Jul '22

22 Jul '22

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=119388 Your paranoid android. === build (build log) === error: patch failed: dlls/user32/message.c:856 error: patch failed: dlls/user32/user_private.h:89 error: patch failed: dlls/user32/winproc.c:719 error: patch failed: dlls/win32u/message.c:2952 error: patch failed: include/ntuser.h:276 error: patch failed: dlls/user32/message.c:877 error: patch failed: dlls/win32u/message.c:2496 error: patch failed: dlls/win32u/sysparams.c:4880 error: patch failed: dlls/win32u/win32u_private.h:436 error: patch failed: include/ntuser.h:902 error: patch failed: dlls/user32/message.c:597 error: patch failed: dlls/win32u/hook.c:60 error: patch failed: dlls/win32u/message.c:109 error: patch failed: dlls/win32u/tests/win32u.c:425 error: patch failed: dlls/win32u/win32u_private.h:391 Task: Patch failed to apply

1 0

Re: [PATCH 3/4] server: Report the socket error in sock_poll_event() on POLLERR or POLLHUP.
by Marvin 22 Jul '22

22 Jul '22

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=119378 Your paranoid android. === build (build log) === error: patch failed: server/sock.c:1090 error: patch failed: server/sock.c:645 error: patch failed: dlls/ws2_32/tests/afd.c:162 error: patch failed: server/sock.c:1145 Task: Patch failed to apply

1 0

Re: [PATCH 1/1] d3d11: Use CRT allocation functions.
by Marvin 22 Jul '22

22 Jul '22

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=119444 Your paranoid android. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: d3d11.c:1570: Test succeeded inside todo block: Got unexpected hr 0. d3d11.c:1570: Test succeeded inside todo block: d3d11.c:1570: Test succeeded inside todo block: Got unexpected hr 0.

1 0

Re: [PATCH 3/3] shell32: Reimplement SHBindToParent.
by Marvin 22 Jul '22

22 Jul '22

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=119430 Your paranoid android. === debian11 (32 bit report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Chinese:China report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (64 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got 00000000DEADBEEF

1 0

Re: [PATCH v4] ntdll: Add RtlGetDeviceFamilyInfoEnum and RtlConvertDeviceFamilyInfoToString
by Kacper Rączy 21 Jul '22

21 Jul '22

Is there anything else to be changed there, to get this accepted? BR, Kacper > > Wiadomość napisana przez Kacper rączy <gfw.kra(a)gmail.com> w dniu 06.07.2022, o godz. 14:10: > > >> === debian11 (64 bit WoW report) === >> ntdll: >> env.c:461: Test failed: wrong end ptr 000000000086195C/0000000000861960 > It also fails without the patch on my machine.

1 0

Re: [PATCH 1/3] wined3d: Do not try to unmap already unmapped BOs in wined3d_buffer_update_sub_resource().
by Marvin 21 Jul '22

21 Jul '22

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=119373 Your paranoid android. === debian11 (build log) === WineRunWineTest.pl:error: The previous 1 run(s) terminated abnormally

1 0

[PATCH 2/2] kernel32: Implement GetFileMUIInfo.
by Dmitry Timoshkov 21 Jul '22

21 Jul '22

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/kernel32/tests/resource.c | 7 ++ dlls/kernelbase/locale.c | 145 ++++++++++++++++++++++++++++++++- 2 files changed, 149 insertions(+), 3 deletions(-) diff --git a/dlls/kernel32/tests/resource.c b/dlls/kernel32/tests/resource.c index 626645a8979..f8a49990e6b 100644 --- a/dlls/kernel32/tests/resource.c +++ b/dlls/kernel32/tests/resource.c @@ -617,6 +617,7 @@ static void test_GetFileMUIInfo(void) ret = GetFileMUIInfo(0, path, info, &size); ok(!ret, "GetFileMUIInfo should fail\n"); ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + todo_wine ok(!size, "got %lu\n", size); ok(info->dwSize == sizeof(*info), "got %lu\n", info->dwSize); ok(!info->dwVersion, "got %08lx\n", info->dwVersion); @@ -653,7 +654,9 @@ static void test_GetFileMUIInfo(void) full_size = 0; SetLastError(0xdeadbeef); ret = GetFileMUIInfo(MUI_QUERY_ALL, path, NULL, &full_size); + todo_wine ok(!ret, "GetFileMUIInfo should fail\n"); + todo_wine ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); memset(buf, 0, sizeof(buf)); @@ -666,7 +669,9 @@ static void test_GetFileMUIInfo(void) ok(!ret, "GetFileMUIInfo should fail\n"); ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + todo_wine ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); + todo_wine ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); memset(buf, 0, sizeof(buf)); @@ -700,8 +705,10 @@ static void test_GetFileMUIInfo(void) ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); ok(!ret, "GetFileMUIInfo should fail\n"); ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + todo_wine ok(size == 0, "got %08lx\n", size); ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + todo_wine ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); diff --git a/dlls/kernelbase/locale.c b/dlls/kernelbase/locale.c index 0c20c858a7a..19c4707cec8 100644 --- a/dlls/kernelbase/locale.c +++ b/dlls/kernelbase/locale.c @@ -5699,15 +5699,154 @@ done: } +typedef struct +{ + DWORD dwSignature; + DWORD dwSize; + DWORD dwVersion; + DWORD unknown1; + DWORD unknown2; + DWORD unknown3; + DWORD dwFileType; + BYTE pServiceChecksum[16]; + BYTE pChecksum[16]; + DWORD unknown4[6]; + DWORD dwTypeNameMainOffset; + DWORD dwTypeNameMainSize; + DWORD dwTypeIDMainOffset; + DWORD dwTypeIDMainSize; + DWORD dwTypeNameMUIOffset; + DWORD dwTypeNameMUISize; + DWORD dwTypeIDMUIOffset; + DWORD dwTypeIDMUISize; + DWORD unknown5; + DWORD unknown6; + DWORD dwLanguageNameOffset; + DWORD dwLanguageNameSize; +} MUI_RC_CONFIG; + /****************************************************************************** * GetFileMUIInfo (kernelbase.@) */ BOOL WINAPI /* DECLSPEC_HOTPATCH */ GetFileMUIInfo( DWORD flags, const WCHAR *path, FILEMUIINFO *info, DWORD *size ) { - FIXME( "stub: %lu, %s, %p, %p\n", flags, debugstr_w(path), info, size ); - SetLastError( ERROR_CALL_NOT_IMPLEMENTED ); - return FALSE; + HMODULE module; + HRSRC rsrc; + MUI_RC_CONFIG *rc_cfg; + DWORD rc_size; + + TRACE( "(%08lx,%s,%p,%p)\n", flags, debugstr_w(path), info, size ); + + if (!size) + { + SetLastError( ERROR_INVALID_PARAMETER ); + return FALSE; + } + + if (info) + { + if (*size < sizeof(FILEMUIINFO)) + { + SetLastError( ERROR_INSUFFICIENT_BUFFER ); + return FALSE; + } + + if (*size != info->dwSize || !info->dwVersion) + { + SetLastError( ERROR_INVALID_PARAMETER ); + return FALSE; + } + } + else if (*size) + { + SetLastError( ERROR_INVALID_PARAMETER ); + return FALSE; + } + + module = LoadLibraryExW( path, 0, LOAD_LIBRARY_AS_IMAGE_RESOURCE | LOAD_LIBRARY_AS_DATAFILE ); + if (!module) return FALSE; + + rsrc = FindResourceW( module, MAKEINTRESOURCEW(1), L"MUI" ); + if (!rsrc) + { + FreeLibrary( module ); + return FALSE; + } + + rc_cfg = LockResource( LoadResource( module, rsrc ) ); + + rc_size = sizeof(*info); + if (flags & MUI_QUERY_RESOURCE_TYPES) + { + rc_size += rc_cfg->dwTypeNameMainSize; + rc_size += rc_cfg->dwTypeIDMainSize; + rc_size += rc_cfg->dwTypeNameMUISize; + rc_size += rc_cfg->dwTypeIDMUISize; + } + if (flags & MUI_QUERY_LANGUAGE_NAME) + rc_size += rc_cfg->dwLanguageNameSize; + + if (info) + { + char *p = (char *)(info + 1); + DWORD offset = sizeof(*info); + + memset( (char *)info + 8, 0, *size - 8 ); /* keep original dwSize/dwVersion */ + + if (flags & MUI_QUERY_TYPE) + info->dwFileType = rc_cfg->dwFileType; + + if (flags & MUI_QUERY_CHECKSUM) + { + memcpy( info->pChecksum, rc_cfg->pChecksum, sizeof(info->pChecksum) ); + memcpy( info->pServiceChecksum, rc_cfg->pServiceChecksum, sizeof(info->pServiceChecksum) ); + } + + if (*size < rc_size) + { + FreeLibrary( module ); + SetLastError( ERROR_INSUFFICIENT_BUFFER ); + return FALSE; + } + + if (flags & MUI_QUERY_RESOURCE_TYPES) + { + info->dwTypeNameMainOffset = offset; + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeNameMainOffset, rc_cfg->dwTypeNameMainSize ); + p += rc_cfg->dwTypeNameMainSize; + offset += rc_cfg->dwTypeNameMainSize; + + info->dwTypeIDMainOffset = offset; + info->dwTypeIDMainSize = rc_cfg->dwTypeIDMainSize / sizeof(DWORD); + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeIDMainOffset, rc_cfg->dwTypeIDMainSize ); + p += rc_cfg->dwTypeIDMainSize; + offset += rc_cfg->dwTypeIDMainSize; + + info->dwTypeNameMUIOffset = offset; + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeNameMUIOffset, rc_cfg->dwTypeNameMUISize ); + p += rc_cfg->dwTypeNameMUISize; + offset += rc_cfg->dwTypeNameMUISize; + + info->dwTypeIDMUIOffset = offset; + info->dwTypeIDMUISize = rc_cfg->dwTypeIDMUISize / sizeof(DWORD); + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeIDMUIOffset, rc_cfg->dwTypeIDMUISize ); + p += rc_cfg->dwTypeIDMUISize; + offset += rc_cfg->dwTypeIDMUISize; + } + + if (flags & MUI_QUERY_LANGUAGE_NAME) + { + info->dwLanguageNameOffset = offset; + memcpy( p, (char *)rc_cfg + rc_cfg->dwLanguageNameOffset, rc_cfg->dwLanguageNameSize ); + } + } + else + *size = rc_size; + + FreeLibrary( module ); + + return TRUE; } -- 2.37.1

1 0

[PATCH 1/2] kernel32/tests: Add some tests for GetFileMUIInfo().
by Dmitry Timoshkov 21 Jul '22

21 Jul '22

MUI_RC_CONFIG layout is based on the description from http://hostagebrain.blogspot.com/2015/11/multilingual-user-interface.html Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/kernel32/tests/resource.c | 235 ++++++++++++++++++++++++++++++++- 1 file changed, 234 insertions(+), 1 deletion(-) diff --git a/dlls/kernel32/tests/resource.c b/dlls/kernel32/tests/resource.c index 6c5bc99c0c5..626645a8979 100644 --- a/dlls/kernel32/tests/resource.c +++ b/dlls/kernel32/tests/resource.c @@ -2,6 +2,7 @@ * Unit test suite for resource functions. * * Copyright 2006 Mike McCormack + * Copyright 2022 Dmitry Timoshkov * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Lesser General Public @@ -18,8 +19,10 @@ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA */ -#include <windows.h> +#include <stdarg.h> #include <stdio.h> +#include <assert.h> +#include <windows.h> #include "wine/test.h" @@ -520,10 +523,240 @@ static void test_internal_structure(void) ok( EndUpdateResourceW( res, TRUE ), "EndUpdateResourceW failed\n"); } +typedef struct +{ + DWORD dwSignature; + DWORD dwSize; + DWORD dwVersion; + DWORD unknown1; + DWORD unknown2; + DWORD unknown3; + DWORD dwFileType; + BYTE pServiceChecksum[16]; + BYTE pChecksum[16]; + DWORD unknown4[6]; + DWORD dwTypeNameMainOffset; + DWORD dwTypeNameMainSize; + DWORD dwTypeIDMainOffset; + DWORD dwTypeIDMainSize; + DWORD dwTypeNameMUIOffset; + DWORD dwTypeNameMUISize; + DWORD dwTypeIDMUIOffset; + DWORD dwTypeIDMUISize; + DWORD unknown5; + DWORD unknown6; + DWORD dwLanguageNameOffset; + DWORD dwLanguageNameSize; +} MUI_RC_CONFIG; + +static void *offset_to_data(void *base, DWORD offset) +{ + return (char *)base + offset; +} + +static void test_GetFileMUIInfo(void) +{ +#define MUI_QUERY_ALL (MUI_QUERY_TYPE | MUI_QUERY_CHECKSUM | MUI_QUERY_LANGUAGE_NAME | MUI_QUERY_RESOURCE_TYPES) + static const BYTE zero[8]; + static const WCHAR path[] = L"urlmon.dll"; + char buf[1024]; + HRSRC rsrc; + MUI_RC_CONFIG *rc_cfg; + char *p1, *p2; + FILEMUIINFO *info = (FILEMUIINFO *)buf; + DWORD size, full_size; + HMODULE module; + int ret; + + module = LoadLibraryExW(path, 0, LOAD_LIBRARY_AS_IMAGE_RESOURCE | LOAD_LIBRARY_AS_DATAFILE); + ok(module != NULL, "LoadLibraryEx error %lu\n", GetLastError()); + rsrc = FindResourceW(module, MAKEINTRESOURCEW(1), L"MUI"); + todo_wine + ok(rsrc != 0, "MUI resource not found\n"); + if (!rsrc) + { + skip("MUI resource not found\n"); + FreeLibrary(module); + return; + } + rc_cfg = LockResource(LoadResource(module, rsrc)); + ok(rc_cfg->dwVersion == MAKELONG(0,1), "got %08lx\n", rc_cfg->dwVersion); + ok(rc_cfg->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", rc_cfg->dwFileType); + + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, NULL, NULL); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + + info->dwSize = sizeof(*info); + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, NULL); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + + size = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, NULL, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + + size = 0; + ret = GetFileMUIInfo(0, path, NULL, &size); + ok(ret, "GetFileMUIInfo error %lu\n", GetLastError()); + ok(size == sizeof(FILEMUIINFO), "got %lu bytes\n", size); + + memset(info, 0, sizeof(*info)); + size = info->dwSize = sizeof(*info) - 1; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + + memset(info, 0, sizeof(*info)); + size = info->dwSize = sizeof(*info); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(!size, "got %lu\n", size); + ok(info->dwSize == sizeof(*info), "got %lu\n", info->dwSize); + ok(!info->dwVersion, "got %08lx\n", info->dwVersion); + + memset(info, 0, sizeof(*info)); + size = info->dwSize = sizeof(*info); + info->dwVersion = MUI_FILEINFO_VERSION; + ret = GetFileMUIInfo(0, path, info, &size); + ok(ret, "GetFileMUIInfo error %lu\n", GetLastError()); + + memset(buf, 0, sizeof(buf)); + size = info->dwSize = 1; + info->dwVersion = MUI_FILEINFO_VERSION; + info->dwFileType = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + ok(info->dwVersion == MUI_FILEINFO_VERSION, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0xdeadbeef, "got %08lx\n", info->dwFileType); + + memset(buf, 0, sizeof(buf)); + info->dwSize = sizeof(*info); + size = sizeof(*info) + 1; + info->dwVersion = MUI_FILEINFO_VERSION; + info->dwFileType = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(info->dwVersion == MUI_FILEINFO_VERSION, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0xdeadbeef, "got %08lx\n", info->dwFileType); + + full_size = 0; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, NULL, &full_size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = sizeof(*info); + info->dwVersion = 0; + info->dwFileType = 0xdeadbeef; + memcpy(info->abBuffer, "deadbeef", 8); + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); + ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = sizeof(*info); + info->dwVersion = 0xdeadbeef; + info->dwFileType = 0xdeadbeef; + memcpy(info->abBuffer, "deadbeef", 8); + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + ok(info->dwVersion == 0xdeadbeef, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", info->dwFileType); + ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = sizeof(*info); + info->dwVersion = 0xdeadbeef; + info->dwFileType = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + ok(info->dwVersion == 0xdeadbeef, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", info->dwFileType); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = full_size; + info->dwVersion = 0; + info->dwFileType = 0xdeadbeef; + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(size == 0, "got %08lx\n", size); + ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); + ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = full_size; + info->dwVersion = MUI_FILEINFO_VERSION; + info->dwFileType = 0xdeadbeef; + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(ret || broken(GetLastError() == ERROR_INSUFFICIENT_BUFFER) /* Some Win10 versions */, "GetFileMUIInfo error %lu\n", GetLastError()); + while (!ret) /* Try to recover from Win10 breakage */ + { + size += 2; + assert(size <= sizeof(buf)); + info->dwSize = size; + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + } + ok(info->dwVersion == MUI_FILEINFO_VERSION, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", info->dwFileType); + + ok(!memcmp(info->pChecksum, rc_cfg->pChecksum, 16), "Checksum doesn't match\n"); + ok(!memcmp(info->pServiceChecksum, rc_cfg->pServiceChecksum, 16), "ServiceChecksum doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwLanguageNameOffset); + p2 = offset_to_data(info, info->dwLanguageNameOffset); + ok(!memcmp(p1, p2, rc_cfg->dwLanguageNameSize), "LanguageName doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeNameMainOffset); + p2 = offset_to_data(info, info->dwTypeNameMainOffset); + ok(!memcmp(p1, p2, rc_cfg->dwTypeNameMainSize), "TypeNameMain doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeIDMainOffset); + p2 = offset_to_data(info, info->dwTypeIDMainOffset); + ok(rc_cfg->dwTypeIDMainSize == info->dwTypeIDMainSize * sizeof(DWORD), "dwTypeIDMainSize %#08lx != %08lx\n", + rc_cfg->dwTypeIDMainSize, info->dwTypeIDMainSize); + ok(!memcmp(p1, p2, rc_cfg->dwTypeIDMainSize), "TypeIDMain doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeIDMUIOffset); + p2 = offset_to_data(info, info->dwTypeIDMUIOffset); + ok(rc_cfg->dwTypeIDMUISize == info->dwTypeIDMUISize * sizeof(DWORD), "dwTypeIDMUISize %#08lx != %08lx\n", + rc_cfg->dwTypeIDMUISize, info->dwTypeIDMUISize); + ok(!memcmp(p1, p2, rc_cfg->dwTypeIDMUISize), "TypeIDMUI doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeNameMUIOffset); + p2 = offset_to_data(info, info->dwTypeNameMUIOffset); + ok(!memcmp(p1, p2, rc_cfg->dwTypeNameMUISize), "TypeNameMUI doesn't match\n"); + + FreeLibrary(module); +} + START_TEST(resource) { DWORD i; + test_GetFileMUIInfo(); + DeleteFileA( filename ); update_missing_exe(); -- 2.37.1

1 0

[PATCH vkd3d 1/2] vkd3d: Delay adding a command queue to the blocked list until after the op is written.
by Conor McCarthy 20 Jul '22

20 Jul '22

Otherwise the following sequence can occur: 1. A command queue is added to the blocked list during a Wait() call. 2. An unblocking Signal() occurs on the CPU in another thread, flushing the blocked ops, but as no op has been written, the queue is removed from the blocked list. 3. The blocked op is written. 3. Another op is queued and the queue is not re-added to the blocked list because this only happens for the first op. World of Warcraft triggers this issue. Signed-off-by: Conor McCarthy <cmccarthy(a)codeweavers.com> --- libs/vkd3d/command.c | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/libs/vkd3d/command.c b/libs/vkd3d/command.c index d0782e5a..7452128c 100644 --- a/libs/vkd3d/command.c +++ b/libs/vkd3d/command.c @@ -6812,12 +6812,6 @@ static HRESULT STDMETHODCALLTYPE d3d12_command_queue_Wait(ID3D12CommandQueue *if * where multiple queues alias over the same physical queue, so effectively, * we need to manage out-of-order submits ourselves. */ - if (!command_queue->ops_count) - hr = d3d12_device_add_blocked_command_queues(command_queue->device, &command_queue, 1); - - if (FAILED(hr)) - goto done; - if (!(op = d3d12_command_queue_require_space_locked(command_queue))) { hr = E_OUTOFMEMORY; @@ -6829,6 +6823,11 @@ static HRESULT STDMETHODCALLTYPE d3d12_command_queue_Wait(ID3D12CommandQueue *if d3d12_fence_incref(fence); + /* Add the queue to the blocked list after writing the op to ensure the queue isn't + * removed again in another thread because it has no ops. */ + if (command_queue->ops_count == 1) + hr = d3d12_device_add_blocked_command_queues(command_queue->device, &command_queue, 1); + done: vkd3d_mutex_unlock(&command_queue->op_mutex); return hr; -- 2.36.1

3 4

[PATCH vkd3d v2 1/3] tests: Test float4 UAV buffer load store.
by Conor McCarthy 20 Jul '22

20 Jul '22

This currently fails if the shader loads from the UAV, because it causes vkd3d-shader to specify the R32ui format instead of Unknown. Signed-off-by: Conor McCarthy <cmccarthy(a)codeweavers.com> --- v2: Make the load/store test independent of the store test. --- tests/d3d12.c | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) diff --git a/tests/d3d12.c b/tests/d3d12.c index ec5cfb20..57e072e4 100644 --- a/tests/d3d12.c +++ b/tests/d3d12.c @@ -20947,6 +20947,56 @@ static void test_typed_buffer_uav(void) 0x00000000, 0x0002100a, 0x00004001, 0x00000020, 0x0002400a, 0x0a0000a4, 0x0011e0f2, 0x00000000, 0x00100006, 0x00000000, 0x00004002, 0x3f000000, 0x3f000000, 0x3f000000, 0x3f000000, 0x0100003e, }; + static const DWORD cs_vec4_code[] = + { +#if 0 + RWBuffer<float4> buffer; + + [numthreads(8, 1, 1)] + void main(uint3 group_id : SV_groupID, uint group_index : SV_GroupIndex) + { + uint global_index = 8 * group_id.x + group_index; + buffer[global_index] = float4(0.5f, 0.625f, 0.75f, 1.0f); + } +#endif + 0x43425844, 0x37e9fa91, 0x11ca38f4, 0x9d4a70b7, 0x4fd05c45, 0x00000001, 0x000000e0, 0x00000003, + 0x0000002c, 0x0000003c, 0x0000004c, 0x4e475349, 0x00000008, 0x00000000, 0x00000008, 0x4e47534f, + 0x00000008, 0x00000000, 0x00000008, 0x58454853, 0x0000008c, 0x00050050, 0x00000023, 0x0100086a, + 0x0400089c, 0x0011e000, 0x00000000, 0x00005555, 0x0200005f, 0x00024000, 0x0200005f, 0x00021012, + 0x02000068, 0x00000001, 0x0400009b, 0x00000008, 0x00000001, 0x00000001, 0x07000023, 0x00100012, + 0x00000000, 0x0002100a, 0x00004001, 0x00000008, 0x0002400a, 0x0a0000a4, 0x0011e0f2, 0x00000000, + 0x00100006, 0x00000000, 0x00004002, 0x3f000000, 0x3f200000, 0x3f400000, 0x3f800000, 0x0100003e, + }; + static const DWORD cs_vec4_load_code[] = + { + /* Compiled with /Od */ +#if 0 + RWBuffer<float4> buffer; + + [numthreads(4, 1, 1)] + void main(uint3 group_id : SV_groupID, uint group_index : SV_GroupIndex) + { + uint global_index = 8 * group_id.x + group_index * 2u; + buffer[global_index] = float4(0.5f, 0.625f, 0.75f, 1.0f); + buffer[global_index + 1] = buffer[global_index]; + } +#endif + 0x43425844, 0x0b7914da, 0x7379094c, 0xa3567660, 0xeb9df127, 0x00000001, 0x000001b0, 0x00000004, + 0x00000030, 0x00000040, 0x00000050, 0x000001a0, 0x4e475349, 0x00000008, 0x00000000, 0x00000008, + 0x4e47534f, 0x00000008, 0x00000000, 0x00000008, 0x58454853, 0x00000148, 0x00050050, 0x00000052, + 0x0100886a, 0x0400089c, 0x0011e000, 0x00000000, 0x00005555, 0x0200005f, 0x00024000, 0x0200005f, + 0x00021012, 0x02000068, 0x00000002, 0x0400009b, 0x00000004, 0x00000001, 0x00000001, 0x05000036, + 0x00100012, 0x00000000, 0x00004001, 0x00000008, 0x07000026, 0x0000d000, 0x00100012, 0x00000000, + 0x0010000a, 0x00000000, 0x0002100a, 0x07000026, 0x0000d000, 0x00100022, 0x00000000, 0x0002400a, + 0x00004001, 0x00000002, 0x0700001e, 0x00100012, 0x00000000, 0x0010001a, 0x00000000, 0x0010000a, + 0x00000000, 0x0a0000a4, 0x0011e0f2, 0x00000000, 0x00100006, 0x00000000, 0x00004002, 0x3f000000, + 0x3f200000, 0x3f400000, 0x3f800000, 0x05000036, 0x00100022, 0x00000000, 0x00004001, 0x00000001, + 0x0700001e, 0x00100022, 0x00000000, 0x0010001a, 0x00000000, 0x0010000a, 0x00000000, 0x890000a3, + 0x80000042, 0x00155543, 0x001000f2, 0x00000001, 0x00100006, 0x00000000, 0x0011ee46, 0x00000000, + 0x070000a4, 0x0011e0f2, 0x00000000, 0x00100556, 0x00000000, 0x00100e46, 0x00000001, 0x0100003e, + 0x30494653, 0x00000008, 0x00000800, 0x00000000, + }; + static const struct vec4 expected = {0.5f, 0.625f, 0.75f, 1.0f}; if (!init_compute_test_context(&context)) return; @@ -21004,6 +21054,48 @@ static void test_typed_buffer_uav(void) check_readback_data_float(&rb.rb, NULL, 0.5f, 0); release_resource_readback(&rb); + reset_command_list(command_list, context.allocator); + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_COPY_SOURCE, D3D12_RESOURCE_STATE_UNORDERED_ACCESS); + ID3D12PipelineState_Release(pipeline_state); + pipeline_state = create_compute_pipeline_state(device, root_signature, + shader_bytecode(cs_vec4_code, sizeof(cs_vec4_code))); + + uav_desc.Format = DXGI_FORMAT_R32G32B32A32_FLOAT; + uav_desc.Buffer.NumElements = 16; + ID3D12Device_CreateUnorderedAccessView(device, resource, NULL, &uav_desc, cpu_descriptor_handle); + + ID3D12GraphicsCommandList_SetPipelineState(command_list, pipeline_state); + ID3D12GraphicsCommandList_SetComputeRootSignature(command_list, root_signature); + ID3D12GraphicsCommandList_SetComputeRootDescriptorTable(command_list, 0, gpu_descriptor_handle); + ID3D12GraphicsCommandList_Dispatch(command_list, 2, 1, 1); + + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_UNORDERED_ACCESS, D3D12_RESOURCE_STATE_COPY_SOURCE); + + get_buffer_readback_with_command_list(resource, uav_desc.Format, &rb, queue, command_list); + check_readback_data_vec4(&rb.rb, NULL, &expected, 0); + release_resource_readback(&rb); + + reset_command_list(command_list, context.allocator); + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_COPY_SOURCE, D3D12_RESOURCE_STATE_UNORDERED_ACCESS); + ID3D12PipelineState_Release(pipeline_state); + pipeline_state = create_compute_pipeline_state(device, root_signature, + shader_bytecode(cs_vec4_load_code, sizeof(cs_vec4_load_code))); + + ID3D12GraphicsCommandList_SetPipelineState(command_list, pipeline_state); + ID3D12GraphicsCommandList_SetComputeRootSignature(command_list, root_signature); + ID3D12GraphicsCommandList_SetComputeRootDescriptorTable(command_list, 0, gpu_descriptor_handle); + ID3D12GraphicsCommandList_Dispatch(command_list, 2, 1, 1); + + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_UNORDERED_ACCESS, D3D12_RESOURCE_STATE_COPY_SOURCE); + + get_buffer_readback_with_command_list(resource, uav_desc.Format, &rb, queue, command_list); + todo check_readback_data_vec4(&rb.rb, NULL, &expected, 0); + release_resource_readback(&rb); + ID3D12Resource_Release(resource); ID3D12RootSignature_Release(root_signature); ID3D12PipelineState_Release(pipeline_state); -- 2.36.1

2 1

How to propagate Linux device ready for read FD state to Wine proxy WDM driver
by Pavel Pisa 20 Jul '22

20 Jul '22

Dear wine developers, I monitor from time to time Wine development state. I have significant interrest to use it for our open-source chromatography processing and control system CHROMuLAN http://pikron.com/pages/products/hplc/chromulan.html . It runs well under wine for years except for minor problem with excessive size of new analysis setup dialog, it is old Delphi 6 app. If somebody is willing to look at it I give more information or setup issue. But uLAN driver access is required to control real devices and acquire data http://ulan.sourceforge.net/ Driver is available in source form from 1996 year and it has been developed and is maintained on GNU/Linux system but with CHROMuLAN windows build from the same sources is used from Windows NT 3.5 days. I have idea in 2013 year to try implement proxy driver which allows to access native Linux kernel driver from Windows application. I have found at that time that Wine protocol is able to deliver data between wine server driver and application only for IOCTLs, read and write calls has not been implemented for device driver file handle type and I have documented problem on WineHQ list https://www.winehq.org/pipermail/wine-devel/2013-July/thread.html#100409 But when I looked into latest Wine sources I have noticed, that it should not be problem anymore. So I have cleaned from the dust old experiment and updated it for actual Wine. Linux driver interaction has been separated from WDM proxy part and marked (ul_l_drv.c) #if 0 #pragma makedep unix #endif unix calls conversion has been added (ul_l_exports.c) const unixlib_entry_t __wine_unix_call_funcs[] = and real WDM has been used as base for the proxy driver (ul_drv.c, device.c). Both originally based on some Wine driver to emulate disk and other behavior. The code is available there https://cmp.felk.cvut.cz/~pisa/ulan/wine/ul_drv.sys/ and it works with whole CHROMuLAN system. Yes, there is lot of space for cleanups, service is started in manual mode unconditionally etc.. [System\\CurrentControlSet\\Services\\ul_drv] 1658091793 ... "Start"=dword:00000001 etc... There is one missing feature and it is wait for arrival of the new messages without periodic polling. It is easy on Linux side, select, poll, epoll can be used for ready for read. In Windows world select does not work for device drivers so IOCTL is used which marks IoMarkIrpPending, then user can wait for associated overlapped event for example by WaitForSingleObject. I have implemented logic in Wine proxy driver and IRP is marked by IoMarkIrpPending, cancellation and all other stuff seems to work. But I need somehow bind event on Linux native file descriptor which is maintained in makedep unix with some way to mark corresponding IRP in Windows driver part as complete IoCompleteRequest(old_irp,IO_NO_INCREMENT); What are the options? Should, can I can start service thread in makedep unix part and call IoCompleteRequest from there? In the fact I would prefer even more only register callback in the Wise server main loop which would be called when Linux device file descriptor is ready to read. Is there some example how to do something like that? What are locking requirements and limitations? It is more for curiosity now, we experimental port to FPC/Lazarus which runs on Linux and Windows now, but on the other hand there are still some features missing in that build, Lazarus with Gtk does not implement MDI in really usable form etc... So there is still some potential for this and other applications using uLAN to be run under Wine. Thanks for your time and best wishes, Pavel -- Pavel Pisa phone: +420 603531357 e-mail: pisa(a)cmp.felk.cvut.cz Department of Control Engineering FEE CVUT Karlovo namesti 13, 121 35, Prague 2 university: https://control.fel.cvut.cz/ company: https://www.pikron.com/ personal: https://cmp.felk.cvut.cz/~pisa projects: https://www.openhub.net/accounts/ppisa CAN related:http://canbus.pages.fel.cvut.cz/ RISC-V education: https://comparch.edu.cvut.cz/ Open Technologies Research Education and Exchange Services https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home

2 1

Re: [PATCH v3 3/3] mfplat/tests: Merge and reorganize image format tests.
by Marvin 20 Jul '22

20 Jul '22

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=119352 Your paranoid android. === w7u_adm (32 bit report) === mfplat: 0864:mfplat: unhandled exception c0000005 at 6ED77D1C === w7u_el (32 bit report) === mfplat: 0858:mfplat: unhandled exception c0000005 at 72467D24

1 0

Re: [PATCH v3 1/3] mfplat/tests: Mark some tests as broken on Win 8 and 10 v1507.
by Marvin 20 Jul '22

20 Jul '22

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=119350 Your paranoid android. === w7u_el (32 bit report) === mfplat: 089c:mfplat: unhandled exception c0000005 at 722C7D1C

1 0

Re: [PATCH 1/4] ws2_32/tests: Test listen() after a failed connect().
by Marvin 20 Jul '22

20 Jul '22

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=119329 Your paranoid android. === w10pro64_ar (64 bit report) === ws2_32: sock.c:6964: Test failed: got apc_count 1.

1 0

Re: [PATCH 6/6] uiautomationcore: Add support for ProviderOptions_UseComThreading flag.
by Marvin 20 Jul '22

20 Jul '22

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=119322 Your paranoid android. === debian11 (32 bit report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Arabic:Morocco report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit German report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit French report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Hebrew:Israel report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Hindi:India report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Japanese:Japan report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Chinese:China report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit WoW report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (64 bit WoW report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4270: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 0 uiautomation.c:4281: Test failed: Unexpected I4 0x75d110 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4270: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 0 uiautomation.c:4281: Test failed: Unexpected I4 0x75d110 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE

1 0

Re: [PATCH 9/9] mshtml: Implement ProgressEvent's total prop.
by Marvin 19 Jul '22

19 Jul '22

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=119309 Your paranoid android. === w10pro64_ja (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS === w1064_tsign (32 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH 8/9] mshtml: Implement ProgressEvent's loaded prop.
by Marvin 19 Jul '22

19 Jul '22

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=119308 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS === w7u_2qxl (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658261179154 expected 1658261179216"

1 0

Re: [PATCH 7/9] mshtml: Implement ProgressEvent's lengthComputable prop.
by Marvin 19 Jul '22

19 Jul '22

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=119307 Your paranoid android. === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658259923855 expected 1658259923918"

1 0

Re: [PATCH 6/9] mshtml: Fix copy-paste mistake in test message.
by Marvin 19 Jul '22

19 Jul '22

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=119306 Your paranoid android. === w10pro64 (32 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS === w7u_2qxl (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658258499697 expected 1658258499760" === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658259134369 expected 1658259134432"

1 0

Re: [PATCH v6 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 19 Jul '22

19 Jul '22

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=119286 Your paranoid android. === debian11 (64 bit WoW report) === user32: win.c:11075: Test failed: Received WM_ACTIVATEAPP(0), did not expect it.

1 0

Re: [PATCH v2 1/1] shell32: Return stub bitmap in IShellItemImageFactory::GetImage.
by Marvin 18 Jul '22

18 Jul '22

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=119269 Your paranoid android. === w1064v1809 (32 bit report) === shell32: shlfolder.c:5007: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064 (32 bit report) === shell32: shlfolder.c:5007: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064_tsign (32 bit report) === shell32: shlfolder.c:5007: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064v1809 (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064_tsign (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_zh_CN (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH 2/2] advapi32/tests: Test kernel object security with the primary token as well.
by Marvin 18 Jul '22

18 Jul '22

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=119261 Your paranoid android. === w7u_2qxl (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w7u_adm (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w7u_el (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w8 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w8adm (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w864 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1507 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1809 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_tsign (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w864 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1507 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1809 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_2qxl (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_adm (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_tsign (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_en_AE_u8 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_ar (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_ja (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_zh_CN (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === debian11 (32 bit report) === Report validation errors: advapi32:security prints too much data (33046 bytes) === debian11 (32 bit Arabic:Morocco report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit German report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit French report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Hebrew:Israel report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Hindi:India report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Japanese:Japan report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Chinese:China report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit WoW report) === Report validation errors: advapi32:security prints too much data (33046 bytes) === debian11 (64 bit WoW report) === Report validation errors: advapi32:security prints too much data (33054 bytes)

1 0

Wine related spam
by Fabian Maurer 18 Jul '22

18 Jul '22

I already told you to not spam random people with wine related mails. Seriously, I'll put you on my instant-delete list and just ignore everything in the future if you don't stop. @Others How do you deal with stuff like this? Just filter it out immediately? Regards, Fabian Maurer On Montag, 18. Juli 2022 10:20:21 CEST you wrote: > Some info from Wine 7.13

2 1

Re: [PATCH v4 2/3] riched20: Add font fallback support.
by Marvin 18 Jul '22

18 Jul '22

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=119249 Your paranoid android. === w10pro64_ar (64 bit report) === riched20: editor.c:5469: Test failed: test paste: strcmp = 1, text='testing paste

1 0

Re: [PATCH v5 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin 18 Jul '22

18 Jul '22

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=119242 Your paranoid android. === w1064_tsign (64 bit report) === user32: win.c:10947: Test failed: pos = 014a015e === w10pro64 (64 bit report) === user32: win.c:10947: Test failed: pos = 014a015e === debian11 (32 bit Hindi:India report) === user32: win.c:8998: Test failed: Unexpected event was delivered

1 0

Re: [PATCH v5 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 18 Jul '22

18 Jul '22

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=119241 Your paranoid android. === w10pro64_ar (64 bit report) === user32: win.c:4641: Test failed: hwnd 000000000005025C/000000000005025C message 0200 win.c:4643: Test failed: wparam 0 win.c:4654: Test failed: hwnd 000000000005025C/000000000005025C message 0203 win.c:4658: Test failed: message 0202 available === w10pro64_ja (64 bit report) === user32: win.c:10957: Test failed: msg.message = 1e

1 0

Re: [PATCH 2/2] urlmon/tests: Trace why the test file creation failed.
by Marvin 18 Jul '22

18 Jul '22

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=119218 Your paranoid android. === w7u_2qxl (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1324 url.c:1492: Test failed: wrong thread 1324 === w7u_adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2172 url.c:1492: Test failed: wrong thread 2172 === w7u_el (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2216 url.c:1466: Test failed: progress 32: status = 200 === w8 (32 bit report) === urlmon: url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 2780 url.c:1492: Test failed: wrong thread 2780 === w8adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2804 url.c:1492: Test failed: wrong thread 2804 === w864 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1204 url.c:1466: Test failed: progress 64: status = 302 url.c:1466: Test failed: progress 3: status = 302 === w1064v1507 (32 bit report) === urlmon: url.c:1462: Test failed: progress 3: hres = 1, expected 0 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (32 bit report) === urlmon: url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7740 url.c:1492: Test failed: wrong thread 7740 === w1064 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7412 url.c:1492: Test failed: wrong thread 7412 url.c:1466: Test failed: progress 64: status = 302 === w1064_tsign (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 8140 url.c:1492: Test failed: wrong thread 8140 url.c:1466: Test failed: progress 64: status = 302 === w10pro64 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7752 url.c:1492: Test failed: wrong thread 7752 === w864 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1466: Test failed: progress 64: status = 200 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 url.c:1640: Test failed: unexpected call OnProgress_FINDINGRESOURCE === w1064v1809 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7512 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7512 === w1064 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7324 url.c:1492: Test failed: wrong thread 7324 url.c:1466: Test failed: progress 64: status = 302 === w1064_2qxl (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7804 url.c:1492: Test failed: wrong thread 7804 url.c:1466: Test failed: progress 64: status = 302 === w1064_adm (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7324 url.c:1466: Test failed: progress 64: status = 302 url.c:1492: Test failed: wrong thread 7324 === w1064_tsign (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 6996 url.c:1492: Test failed: wrong thread 6996 === w10pro64 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7652 url.c:1492: Test failed: wrong thread 7652 === w10pro64_en_AE_u8 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5892 url.c:1492: Test failed: wrong thread 5892 === w10pro64_ar (64 bit report) === urlmon: url.c:1492: Test failed: url.c:1662: Test failed: unexpected call OnProgress_REDIRECTING url.c:1492: Test failed: wrong thread 8292 === w10pro64_ja (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3088 url.c:1466: Test failed: progress 64: status = 302 url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 3088 === w10pro64_zh_CN (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4540 url.c:1492: Test failed: wrong thread 4540

1 0

Re: [PATCH 4/5] urlmon/tests: Fix the spelling of a trace() message.
by Marvin 18 Jul '22

18 Jul '22

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=119211 Your paranoid android. === w7u_2qxl (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1276 url.c:1492: Test failed: wrong thread 1124 === w7u_adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2196 url.c:1492: Test failed: wrong thread 2200 === w7u_el (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2212 url.c:1492: Test failed: wrong thread 2256 === w8 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2896 url.c:1492: Test failed: wrong thread 2896 === w8adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2512 url.c:1492: Test failed: url.c:1796: Test failed: wrong thread 2512 === w864 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2708 url.c:1492: Test failed: wrong thread 2708 url.c:1466: Test failed: progress 64: status = 200 === w1064v1507 (32 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (32 bit report) === urlmon: url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7732 url.c:1492: Test failed: wrong thread 7732 url.c:1466: Test failed: progress 64: status = 200 === w1064 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7380 url.c:1492: Test failed: wrong thread 7380 url.c:1466: Test failed: progress 64: status = 302 === w1064_tsign (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7684 url.c:1492: Test failed: wrong thread 7684 url.c:1466: Test failed: progress 64: status = 302 === w10pro64 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7752 url.c:1492: Test failed: wrong thread 7752 === w864 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1796: Test failed: unexpected code 64 url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 3032 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 3: status = 200 url.c:1466: Test failed: progress 32: status = 200 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7576 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7576 === w1064 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7304 url.c:1466: Test failed: progress 64: status = 302 === w1064_2qxl (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7708 url.c:1466: Test failed: progress 64: status = 302 url.c:1492: Test failed: wrong thread 7708 === w1064_adm (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5924 url.c:1492: Test failed: wrong thread 5924 === w1064_tsign (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4076 url.c:1462: Test failed: progress 3: hres = 1, expected 0 url.c:1466: Test failed: progress 32: status = 200 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1492: Test failed: wrong thread 4076 url.c:1466: Test failed: progress 64: status = 200 === w10pro64 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7668 url.c:1492: Test failed: wrong thread 7668 === w10pro64_en_AE_u8 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2848 url.c:1492: Test failed: wrong thread 2848 === w10pro64_ar (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5872 url.c:1492: Test failed: wrong thread 5872 === w10pro64_ja (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4472 url.c:1492: Test failed: wrong thread 4472 url.c:1466: Test failed: progress 64: status = 302 === w10pro64_zh_CN (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 8316 url.c:1492: Test failed: wrong thread 8316

1 0

'wrc' weirdness
by Gisle Vanem 17 Jul '22

17 Jul '22

Hello again list. I'm still struggling with understanding the build of Wine on Win-10 using MSVC or clang-cl. E.g. the 'wrc' program behaves rather different from MSVC's 'rc'. When for example using 'wrc' to build 'attrib.exe', the output of 'attrib.exe /?' looks like this: ATTRIB - Displays or changes file attributes. Syntax: ATTRIB [+R | -R] [+A | -A ] [+S | -S] [+H | -H] [drive:][path][filename] [/S [/D]] Where: + Sets an attribute. ---------------- All lines are doubled up (?!). But using 'rc', there is this issue: ATTRIB - Displays or changes file attributes. Syntax: ATTRIB [+R | -R] [+A | -A ] [+S | -S] [+H | -H] [drive:][path][filename] \ [/S [/D]] \Where: \ + Sets an attribute. \ - Clears an attribute. -------------- The extra '\' at each line (!?). I've tried converting 'attrib.rc' to Unix/DOS line-endings to no avail. And BTW, I used: wrc -D__WINESRC__ -I../../include --output objdir/attrib.res attrib.rc to compile it. What is going on with this, please? -- --gv

2 4

[PATCH v3 1/2] qedit/tests: Test adding a reference to the sample from ISampleGrabberCB::SampleCB().
by Zebediah Figura 17 Jul '22

17 Jul '22

From: Brendan McGrath <brendan(a)redmandi.com> Unravel Two adds a reference to the IMediaSample during its callback. This patch adds a test that checks if an application does do this, that it can free it later and the reference count will finish at zero. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51616 Signed-off-by: Brendan McGrath <brendan(a)redmandi.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> --- v3: Some stylistic fixups; make commit messages a bit more specific. dlls/qedit/tests/mediadet.c | 28 +++++++++++++++++++++++----- 1 file changed, 23 insertions(+), 5 deletions(-) diff --git a/dlls/qedit/tests/mediadet.c b/dlls/qedit/tests/mediadet.c index 3202baca924..6e7017f865c 100644 --- a/dlls/qedit/tests/mediadet.c +++ b/dlls/qedit/tests/mediadet.c @@ -866,6 +866,17 @@ static void test_put_filter(void) ok(!ref, "Got outstanding refcount %ld.\n", ref); } +struct test_sample +{ + IMediaSample sample; + LONG refcount; +}; + +static struct test_sample *impl_from_IMediaSample(IMediaSample *iface) +{ + return CONTAINING_RECORD(iface, struct test_sample, sample); +} + static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, void **ppvObject) { @@ -874,12 +885,14 @@ static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, static ULONG WINAPI ms_AddRef(IMediaSample *iface) { - return 2; + struct test_sample *sample = impl_from_IMediaSample(iface); + return InterlockedIncrement(&sample->refcount); } static ULONG WINAPI ms_Release(IMediaSample *iface) { - return 1; + struct test_sample *sample = impl_from_IMediaSample(iface); + return InterlockedDecrement(&sample->refcount); } static HRESULT WINAPI ms_GetPointer(IMediaSample *iface, BYTE **ppBuffer) @@ -989,7 +1002,7 @@ static const IMediaSampleVtbl my_sample_vt = { ms_SetMediaTime }; -static IMediaSample my_sample = { &my_sample_vt }; +static struct test_sample my_sample = { {&my_sample_vt}, 0 }; static BOOL samplecb_called = FALSE; @@ -1012,8 +1025,9 @@ static ULONG WINAPI sgcb_Release(ISampleGrabberCB *iface) static HRESULT WINAPI sgcb_SampleCB(ISampleGrabberCB *iface, double SampleTime, IMediaSample *pSample) { - ok(pSample == &my_sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); + ok(pSample == &my_sample.sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); samplecb_called = TRUE; + IMediaSample_AddRef(pSample); return E_NOTIMPL; } @@ -1043,6 +1057,7 @@ static void test_samplegrabber(void) IEnumPins *pins; HRESULT hr; FILTER_STATE fstate; + ULONG refcount; /* Invalid RIID */ hr = CoCreateInstance(&CLSID_SampleGrabber, NULL, CLSCTX_INPROC_SERVER, &IID_IClassFactory, @@ -1074,10 +1089,13 @@ static void test_samplegrabber(void) hr = IPin_QueryInterface(pin, &IID_IMemInputPin, (void**)&inpin); ok(hr == S_OK, "Got hr %#lx.\n", hr); - hr = IMemInputPin_Receive(inpin, &my_sample); + hr = IMemInputPin_Receive(inpin, &my_sample.sample); ok(hr == S_OK, "Got hr %#lx.\n", hr); ok(samplecb_called == TRUE, "SampleCB should have been called\n"); + refcount = IUnknown_Release(&my_sample.sample); + todo_wine ok(!refcount, "Got unexpected refcount %ld.\n", refcount); + IMemInputPin_Release(inpin); IPin_Release(pin); -- 2.36.1

3 4

Re: [PATCH v3 3/5] dlls/msvcrt: fix and cleanup undecoration of templatized functions and methods
by Marvin 16 Jul '22

16 Jul '22

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. 1 TestBot errors prevented a full analysis of your patch. If the test caused the operating system (e.g. Windows) to crash or reboot you will probably have to modify it to avoid that. Other issues should be reported to the TestBot administrators. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119173 Your paranoid android. === build (build log) === WineRunBuild.pl:error: An error occurred while waiting for the build to complete: network read timed out (wait2:ListSize:0/4) WineRunBuild.pl:error: BotError: The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died)

1 0

Wine staging 7.13 release
by Alistair Leslie-Hughes 16 Jul '22

16 Jul '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.13 (543 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Added: * None Updated: * None Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: [PATCH v2 2/5] msvcrt: add support for C++11 operator "" in demangling
by Marvin 16 Jul '22

16 Jul '22

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=119164 Your paranoid android. === w1064v1507 (32 bit report) === ucrtbase: cpp.c:207: Test failed: unDName returned "??__K_l@@YA?AUCC@@I@Z" for #2 === w1064v1507 (64 bit report) === ucrtbase: cpp.c:207: Test failed: unDName returned "??__K_l@@YA?AUCC@@I@Z" for #2

1 0

Re: [PATCH 3/3] taskschd: Return SCHED_S_TASK_HAS_NOT_RUN from regtask_get_LastRunTime() stub.
by Marvin 16 Jul '22

16 Jul '22

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=119160 Your paranoid android. === w7u_adm (32 bit report) === taskschd: scheduler.c:791: Test failed: DeleteTask error 0x80070005 scheduler.c:787: Test failed: 1: expected 0, got 0x800700b7 scheduler.c:787: Test failed: 2: expected 0x80070002, got 0 scheduler.c:791: Test failed: DeleteTask error 0x80070005 scheduler.c:791: Test failed: DeleteTask error 0x80070005 scheduler.c:807: Test failed: RegisterTask error 0x800700b7 scheduler.c:953: Test failed: DeleteTask error 0x80070005 scheduler.c:955: Test failed: DeleteTask error 0x80070005 scheduler.c:958: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel