August 2022 - Wine-Devel - list.winehq.org

Re: [PATCH 5/6] widl: Simplify handling of already parsed imports.

by Marvin

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

Aug. 1, 2022

Re: [PATCH 4/6] widl: Use a struct list to keep imported files.

by Marvin

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

Aug. 1, 2022

Re: [PATCH 3/6] widl: Move output generation calls out of parser.y.

by Marvin

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

Aug. 1, 2022

Re: [PATCH 1/3] mshtml: Implement window.matchMedia() with MediaQueryList stub.

by Marvin

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

Aug. 1, 2022

Re: [PATCH 2/3] shell32: Add SHBindToFolderIDListParent tests.

by Marvin

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

Aug. 1, 2022