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)
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.
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
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
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=119159
Your paranoid android.
=== w7u_adm (32 bit report) ===
taskschd:
scheduler.c:790: Test failed: DeleteTask error 0x80070005
scheduler.c:786: Test failed: 1: expected 0, got 0x800700b7
scheduler.c:786: Test failed: 2: expected 0x80070002, got 0
scheduler.c:790: Test failed: DeleteTask error 0x80070005
scheduler.c:790: Test failed: DeleteTask error 0x80070005
scheduler.c:806: Test failed: RegisterTask error 0x800700b7
scheduler.c:937: Test failed: DeleteTask error 0x80070005
scheduler.c:939: Test failed: DeleteTask error 0x80070005
scheduler.c:942: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005
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=119152
Your paranoid android.
=== debian11 (32 bit Japanese:Japan report) ===
ws2_32:
sock.c:6295: Test succeeded inside todo block: expected timeout
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=119127
Your paranoid android.
=== w1064_2qxl (64 bit report) ===
shell32:
shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2)
=== w10pro64 (64 bit report) ===
shell32:
shlfolder.c:4991: Test failed: MKDIR: expected notification type 8, 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
shlfolder.c:4991: Test failed: MKDIR: expected notification type 8, got: 40000
=== w10pro64_zh_CN (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=119126
Your paranoid android.
=== w1064v1809 (32 bit report) ===
shell32:
shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000
=== w1064v1809 (64 bit report) ===
shell32:
shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000
=== w1064 (64 bit report) ===
shell32:
shlfolder.c:4991: Test failed: MKDIR: expected notification type 8, 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: MKDIR: expected notification type 8, got: 40000
=== w10pro64_ja (64 bit report) ===
shell32:
shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2)
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=119099
Your paranoid android.
=== w1064v1507 (32 bit report) ===
ws2_32:
protocol.c:2067: Test failed: wait failed
protocol.c:2069: Test failed: overlapped result is 10036
protocol.c:2071: Test failed: overlapped.Internal = 2734
protocol.c:2073: Test failed: got 0