- Wine-Devel - list.winehq.org

Re: [PATCH v2 3/7] ws2_32/tests: Test send() after TCP reset.
by Marvin Aug. 2, 2022

Aug. 2, 2022

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=120344 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

1 0

Re: [PATCH v2 1/7] ws2_32/tests: Test sending data to a peer is closed().
by Marvin Aug. 2, 2022

Aug. 2, 2022

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=120342 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

1 0

Re: [PATCH v6 3/3] cabinet: Implement GetDllVersion implement GetDllVersion, use DllGetVersion as helper function to retreiv
by Marvin Aug. 1, 2022

Aug. 1, 2022

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=120332 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 v6 2/3] cabinet: implement DllGetVersion correctly implement DllGetVersion with correct parameter and behaviour c
by Marvin Aug. 1, 2022

Aug. 1, 2022

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

1 0

Re: [PATCH v6 1/3] cabinet: test GetDllVersion & DllGetVersion Tests are expected to fail as: DllGetVersion isn't implemente
by Marvin Aug. 1, 2022

Aug. 1, 2022

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).

1 0

Re: [PATCH 3/3] mshtml: Implement MediaQueryList's matches prop.
by Marvin Aug. 1, 2022

Aug. 1, 2022

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

1 0

Re: [PATCH 2/3] mshtml: Implement MediaQueryList's media prop.
by Marvin Aug. 1, 2022

Aug. 1, 2022

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

1 0

Re: [PATCH 6/6] widl: Use a struct list for the import stack.
by Marvin Aug. 1, 2022

Aug. 1, 2022

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

1 0

Re: [PATCH 5/6] widl: Simplify handling of already parsed imports.
by Marvin Aug. 1, 2022

Aug. 1, 2022

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 Aug. 1, 2022

Aug. 1, 2022

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