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=120331
Your paranoid android.
=== debian11 (build log) ===
../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’
Task: The win32 Wine build failed
=== debian11 (build log) ===
../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’
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=120330
Your paranoid android.
=== debian11 (32 bit report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit Arabic:Morocco report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit German report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit French report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit Hebrew:Israel report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit Hindi:India report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit Japanese:Japan report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit Chinese:China report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (32 bit WoW report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6).
=== debian11 (64 bit WoW report) ===
cabinet:
version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203.
version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly!
version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203.
version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203.
Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).
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=120307
Your paranoid android.
=== w1064v1809 (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 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=120306
Your paranoid android.
=== w10pro64_en_AE_u8 (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 full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=120323
Your paranoid android.
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
Task: The win32 Wine build failed
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
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=120322
Your paranoid android.
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
Task: The win32 Wine build failed
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
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=120321
Your paranoid android.
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
Task: The win32 Wine build failed
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
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=120320
Your paranoid android.
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
Task: The win32 Wine build failed
=== debian11 (build log) ===
tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’
../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’
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=120305
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: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
=== 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=120263
Your paranoid android.
=== w1064v1809 (64 bit report) ===
shell32:
shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000
=== w1064_tsign (64 bit report) ===
shell32:
shlfolder.c:5009: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2)
=== w10pro64_zh_CN (64 bit report) ===
shell32:
shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000