- Wine-devel - list.winehq.org

Re: [PATCH 5/6] widl: Simplify handling of already parsed imports.
by Marvin 01 Aug '22

01 Aug '22

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

1 0

Re: [PATCH 4/6] widl: Use a struct list to keep imported files.
by Marvin 01 Aug '22

01 Aug '22

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

1 0

Re: [PATCH 3/6] widl: Move output generation calls out of parser.y.
by Marvin 01 Aug '22

01 Aug '22

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

1 0

Re: [PATCH 1/3] mshtml: Implement window.matchMedia() with MediaQueryList stub.
by Marvin 01 Aug '22

01 Aug '22

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

1 0

Re: [PATCH 2/3] shell32: Add SHBindToFolderIDListParent tests.
by Marvin 01 Aug '22

01 Aug '22

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

1 0

Re: [PATCH v2 2/4] bcrypt/tests: Test for BCryptEncrypt with RSA keys.
by Marvin 31 Jul '22

31 Jul '22

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=120255 Your paranoid android. === debian11 (32 bit report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Arabic:Morocco report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit German report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit French report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hebrew:Israel report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hindi:India report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Japanese:Japan report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Chinese:China report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (64 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same

1 0

Re: [PATCH 2/4] bcrypt/tests: Test for BCryptEncrypt with RSA keys.
by Marvin 31 Jul '22

31 Jul '22

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=120251 Your paranoid android. === debian11 (32 bit report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Arabic:Morocco report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit German report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit French report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hebrew:Israel report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hindi:India report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Japanese:Japan report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Chinese:China report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (64 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same

1 0

Re: [PATCH v2 1/1] cabinet.dll: implement DllGetVersion & GetDllVersion Fix stub DllGetVersion implementation to read Dll ve
by Marvin 31 Jul '22

31 Jul '22

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=120249 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

1 0

Re: [PATCH 1/1] cabinet.dll: implement DllGetVersion & GetDllVersion Fix stub DllGetVersion implementation to read Dll versi
by Marvin 31 Jul '22

31 Jul '22

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=120247 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w8 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w8adm (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w864 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w864 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === 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

1 0

Re: [PATCH v2 01/11] winmm/tests: Add tests for visibility of video window.
by Marvin 31 Jul '22

31 Jul '22

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=120234 Your paranoid android. === w8 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0