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=119863
Your paranoid android.
=== w10pro64_zh_CN (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
=== w7u_adm (32 bit report) ===
mshtml:
script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658941745587 expected 1658941745649"
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=119862
Your paranoid android.
=== w10pro64_en_AE_u8 (64 bit report) ===
mshtml:
script.c:3119: Test failed: ReportResult failed: 80ef0001
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=119907
Your paranoid android.
=== debian11 (build log) ===
../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER)
<command-line>: error: expected identifier or ‘(’ before numeric constant
Task: The win32 Wine build failed
=== debian11 (build log) ===
../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER)
<command-line>: error: expected identifier or ‘(’ before numeric constant
Task: The wow64 Wine build failed
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=119901
Your paranoid android.
=== debian11 (build log) ===
../wine/dlls/msvcrt/cpp.c:651:19: error: _MSVCR_VER:
../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER)
<command-line>: error: expected identifier or ‘(’ before numeric constant
Task: The win32 Wine build failed
=== debian11 (build log) ===
../wine/dlls/msvcrt/cpp.c:651:19: error: _MSVCR_VER:
../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER)
<command-line>: error: expected identifier or ‘(’ before numeric constant
Task: The wow64 Wine build failed
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=119861
Your paranoid android.
=== w10pro64_ja (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=119860
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
=== w10pro64_ar (64 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=119828
Your paranoid android.
=== w10pro64_ja (64 bit report) ===
user32:
win.c:189: Test failed: didn't get start_event
win.c:10436: Test failed: WindowFromPoint returned 00000000000902BA, expected 0000000000000000
win.c:10444: Test failed: WindowFromPoint returned 00000000000902BA, expected 0000000000000000
win.c:10447: Test failed: Timed out waiting for the child process
win.c:10345: Test failed: WindowFromPoint returned 00000000000302B2, expected 00000000000902BA
win.c:10352: Test failed: WindowFromPoint returned 00000000000302B2, expected 00000000000401F0
win.c:10358: Test failed: CreateWindowEx failed
win.c:10373: Test failed: transparent window didn't get WM_NCHITTEST message
=== debian11 (32 bit WoW report) ===
user32:
win.c:9024: Test failed: Did not receive WM_KILLFOCUS
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=119827
Your paranoid android.
=== w8adm (32 bit report) ===
user32:
win.c:2688: Test failed: style 0x200000: expected !100
win.c:2688: Test failed: style 0x300000: expected !100
=== w1064 (64 bit report) ===
user32:
win.c:10976: Test failed: pos = 01400154
=== debian11 (32 bit report) ===
user32:
win.c:9026: Test failed: Did not receive WM_KILLFOCUS
=== debian11 (32 bit WoW report) ===
user32:
win.c:9026: Test failed: Did not receive WM_KILLFOCUS