- Wine-Devel - list.winehq.org

Re: [PATCH 1/2] rpcrt4/tests: Add I_RpcBindingInqLocalClientPID() tests.
by Marvin July 14, 2022

July 14, 2022

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=118991 Your paranoid android. === w1064_tsign (32 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w1064 (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w1064_2qxl (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w1064_tsign (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w10pro64 (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w10pro64_en_AE_u8 (64 bit report) === rpcrt4: 0958:server: unhandled exception 000006be at 00007FF99B7B4F69 === w10pro64_ja (64 bit report) === rpcrt4: 0ef4:server: unhandled exception 000006be at 00007FFA40864F69

1 0

Re: [PATCH 7/7] shell32: Implement SHOpenFolderAndSelectItems().
by Marvin July 14, 2022

July 14, 2022

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=118986 Your paranoid android. === w1064v1809 (32 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064 (32 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064_tsign (32 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064v1809 (64 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ar (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 4000000 shlfolder.c:4999: Test failed: Expected PIDL to be NULL shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH 6/7] shell32/tests: Add SHOpenFolderAndSelectItems() tests.
by Marvin July 14, 2022

July 14, 2022

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=118985 Your paranoid android. === w1064v1809 (32 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 4000000 shlfolder.c:4999: Test failed: Expected PIDL to be NULL === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ar (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ja (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH v2 6/6] kernelbase: Implement PrefetchVirtualMemory.
by Marvin July 14, 2022

July 14, 2022

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=118952 Your paranoid android. === debian11 (build log) === error: patch failed: include/winbase.h:1760 error: patch failed: include/winnt.h:788 error: patch failed: include/winternl.h:1993 error: patch failed: tools/winapi/win32.api:3245 error: patch failed: dlls/ntdll/tests/virtual.c:41 error: patch failed: dlls/ntdll/ntdll.spec:388 error: patch failed: dlls/ntdll/unix/loader.c:310 error: patch failed: dlls/wow64/struct32.h:650 error: patch failed: dlls/wow64/syscall.h:211 error: patch failed: dlls/wow64/virtual.c:33 error: patch failed: dlls/kernel32/tests/virtual.c:37 error: patch failed: dlls/kernel32/tests/virtual.c:4231 error: patch failed: dlls/kernelbase/memory.c:415 Task: Patch failed to apply === debian11 (build log) === error: patch failed: include/winbase.h:1760 error: patch failed: include/winnt.h:788 error: patch failed: include/winternl.h:1993 error: patch failed: tools/winapi/win32.api:3245 error: patch failed: dlls/ntdll/tests/virtual.c:41 error: patch failed: dlls/ntdll/ntdll.spec:388 error: patch failed: dlls/ntdll/unix/loader.c:310 error: patch failed: dlls/wow64/struct32.h:650 error: patch failed: dlls/wow64/syscall.h:211 error: patch failed: dlls/wow64/virtual.c:33 error: patch failed: dlls/kernel32/tests/virtual.c:37 error: patch failed: dlls/kernel32/tests/virtual.c:4231 error: patch failed: dlls/kernelbase/memory.c:415 Task: Patch failed to apply

1 0

Re: [PATCH v8 7/7] ntoskrnl: Set device ContainerID from driver
by Marvin July 14, 2022

July 14, 2022

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=118939 Your paranoid android. === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

Re: [PATCH 1/4] ws2_32/tests: Add some tests for NtReadFile() and NtWriteFile() on sockets.
by Marvin July 14, 2022

July 14, 2022

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=118995 Your paranoid android. === debian11 (32 bit Hebrew:Israel report) === ws2_32: afd.c:2716: Test failed: got size 5

1 0

Re: [PATCH 2/2] rpcrt4: Implement I_RpcBindingInqLocalClientPID().
by Marvin July 13, 2022

July 13, 2022

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=118992 Your paranoid android. === w864 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064_tsign (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064_tsign (64 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64 (64 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64_en_AE_u8 (64 bit report) === rpcrt4: 0e54:server: unhandled exception 000006be at 00007FF99B7B4F69

1 0

Re: [PATCH v8 2/7] ntoskrnl/tests: Add test for getting SPDRP_BASE_CONTAINERID from PnP driver
by Marvin July 13, 2022

July 13, 2022

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=118934 Your paranoid android. === debian11 (32 bit Hindi:India report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

Re: [PATCH v7 7/7] ntoskrnl: Set device ContainerID from driver
by Marvin July 13, 2022

July 13, 2022

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=118932 Your paranoid android. === w7u_2qxl (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === w7u_el (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === w8 (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === w1064_tsign (64 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === debian11 (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 driver_pnp.c:706: Test failed: Got 1 remove events. === debian11 (32 bit Arabic:Morocco report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit German report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit French report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 driver_pnp.c:706: Test failed: Got 1 remove events. === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit Hindi:India report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit Japanese:Japan report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit Chinese:China report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (64 bit WoW report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39

1 0

Re: [PATCH v7 2/7] ntoskrnl/tests: Add test for getting SPDRP_BASE_CONTAINERID from PnP driver
by Marvin July 13, 2022

July 13, 2022

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=118927 Your paranoid android. === debian11 (32 bit French report) === ntoskrnl.exe: driver_pnp.c:736: Test failed: expected IRP_MN_REMOVE_DEVICE === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events. === debian11 (32 bit Hindi:India report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0