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=119030
Your paranoid android.
=== w10pro64_en_AE_u8 (64 bit report) ===
user32:
win.c:4400: Test failed: message 0200 available
=== debian11 (32 bit report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit Arabic:Morocco report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit German report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit French report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit Hebrew:Israel report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit Hindi:India report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit Japanese:Japan report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit Chinese:China report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (32 bit WoW report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
=== debian11 (64 bit WoW report) ===
user32:
win.c:8961: Test failed: Last error unexpectedly set to 0
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=119010
Your paranoid android.
=== w1064_tsign (32 bit report) ===
rpcrt4:
server.c:2270: Test failed: RpcBindingFree
=== w1064_tsign (64 bit report) ===
rpcrt4:
server.c:2270: Test failed: RpcBindingFree
=== w10pro64_ja (64 bit report) ===
rpcrt4:
14fc:server: unhandled exception 000006be at 00007FFA40864F69
=== w10pro64_zh_CN (64 bit report) ===
rpcrt4:
2048:server: unhandled exception 000006be at 00007FFD3A124F69
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=119011
Your paranoid android.
=== w8adm (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_adm (64 bit report) ===
rpcrt4:
1ae0:server: unhandled exception 000006be at 00007FFAE69F4F69
=== w1064_tsign (64 bit report) ===
rpcrt4:
server.c:2263: Test failed: RpcBindingFree
=== w10pro64_en_AE_u8 (64 bit report) ===
rpcrt4:
0460:server: unhandled exception 000006be at 00007FF99B7B4F69
=== w10pro64_zh_CN (64 bit report) ===
rpcrt4:
16a8:server: unhandled exception 000006be at 00007FFD3A124F69
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
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
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
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.
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
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