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=118911
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w7u_el (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w8 (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w1064_tsign (64 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
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=118906
Your paranoid android.
=== debian11 (32 bit 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=118887
Your paranoid android.
=== w8adm (32 bit report) ===
ddraw:
ddraw7.c:18840: Test failed: Got unexpected color 0x00000040.
ICMP over SOCK_DGRAM is already used in ndispproxy.sys. But apps may also use ICMP directly over SOCK_RAW (Hardspace: Shipbreaker is an example) and that requires admin privileges on Linux (or setcap cap_net_raw+ep on wineserver).
AF_INET / SOCK_RAW / IPPROTO_ICMP works on Windows without admin privileges.
Comments:
- IP, ICMP header structures and chksum() functions are taken from ndisproxy.sys:icmp_echo.c;
- ICMP over DGRAM, while designed specifically to allow ICMP without admin permissions, still needs some setup Linux, /proc/sys/net/ipv4/ping_group_range controls that. Such socket creation fails on Testbot Debian machines so I left skip() path in test_icmp();
- Linux substitute local port number instead of provided ICMP packet id, while the referenced game depends on reply id matching the id it provided in request. So the last part performs the fixup.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/384
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=118863
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w7u_el (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w8 (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w1064_tsign (64 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== 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=118840
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w7u_el (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== w8 (32 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
ntoskrnl.c:1702: Test failed: got 0 child removal messages
ntoskrnl.c:1719: Test failed: got 0 child removal messages
=== w1064_tsign (64 bit report) ===
ntoskrnl.exe:
ntoskrnl.c:1654: Test failed: got size 78
ntoskrnl.c:1655: Test failed: got container ID "{"
=== 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 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=118824
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
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=118839
Your paranoid android.
=== debian11 (32 bit report) ===
ntoskrnl.exe:
driver_pnp.c:703: 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=118837
Your paranoid android.
=== debian11 (64 bit WoW report) ===
ntoskrnl.exe:
driver_pnp.c:703: 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=118823
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