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
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.
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
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.
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=118924
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 1657738156862 expected 1657738156925"
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=118970
Your paranoid android.
=== w1064_2qxl (64 bit report) ===
user32:
win.c:4579: Test failed: hwnd 000000000001024C/000000000001024C message 0200
win.c:4583: Test failed: hwnd 000000000001024C/000000000001024C message 0201
win.c:4592: Test failed: hwnd 00000000001002B8/00000000001002B8 message 0202
win.c:4595: Test failed: hwnd 00000000001002B8/00000000001002B8 message 0201
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=118923
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
htmldoc.c:350: Test failed: expected Exec_SETTITLE
htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE
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=118922
Your paranoid android.
=== w10pro64_ar (64 bit report) ===
mshtml:
htmldoc.c:2541: Test failed: unexpected call UpdateUI
htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS
htmldoc.c:350: Test failed: expected Exec_SETTITLE
htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE