- Wine-Devel - list.winehq.org

Re: [PATCH v2 4/9] mshtml: Implement hasAttributeNS for Elements.
by Marvin July 27, 2022

July 27, 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=119862 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH v17 6/6] tmp
by Marvin July 27, 2022

July 27, 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=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

1 0

Re: [PATCH v16 6/6] tmp
by Marvin July 27, 2022

July 27, 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=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

1 0

Re: [PATCH v2 3/9] mshtml: Implement removeAttributeNS for Elements.
by Marvin July 27, 2022

July 27, 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=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

1 0

Re: [PATCH v2 2/9] mshtml: Implement setAttributeNS for Elements.
by Marvin July 27, 2022

July 27, 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=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

1 0

Re: [PATCH v7 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin July 27, 2022

July 27, 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=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

1 0

Re: [PATCH v7 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin July 27, 2022

July 27, 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=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

1 0

Re: [PATCH 2/3] mfplat/tests: Test IMF2DBuffer2::Copy2DTo().
by Marvin July 27, 2022

July 27, 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=119796 Your paranoid android. === w7u_adm (32 bit report) === mfplat: 085c:mfplat: unhandled exception c0000005 at 6EFC7D1C === w7u_el (32 bit report) === mfplat: 0858:mfplat: unhandled exception c0000005 at 72117D1C

1 0

Re: [PATCH v4 1/5] dinput/tests: Wait for Acquire to complete when injecting input.
by Marvin July 27, 2022

July 27, 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=119790 Your paranoid android. === w1064_tsign (64 bit report) === dinput: joystick8.c:1606: Test failed: 0x500: WaitForSingleObject failed joystick8.c:1610: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1668: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1669: Test failed: 0x500: got lX 20779 joystick8.c:1670: Test failed: 0x500: got lY 20779 joystick8.c:1671: Test failed: 0x500: got lZ 32767 joystick8.c:1726: Test failed: 0x500: SetProperty DIPROP_JOYSTICKID returned 0x80004001 joystick8.c:1728: Test failed: 0x500: SetProperty DIPROP_AXISMODE returned 0x80070057 joystick8.c:1730: Test failed: 0x500: SetProperty DIPROP_BUFFERSIZE returned 0 joystick8.c:1732: Test failed: 0x500: SetProperty DIPROP_AUTOCENTER returned 0x80070057 joystick8.c:1802: Test failed: 0x500: state[0]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[0]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[0]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[0]: got lZ 32767 joystick8.c:1802: Test failed: 0x500: state[1]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[1]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[1]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[1]: got lZ 32767 joystick8.c:1822: Test failed: 0x500: state[1]: WaitForSingleObject failed joystick8.c:1802: Test failed: 0x500: state[2]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[2]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[2]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[2]: got lZ 32767 joystick8.c:1811: Test failed: 0x500: state[2]: got rgdwPOV[0] -1 joystick8.c:1813: Test failed: 0x500: state[2]: got rgbButtons[0] 0 joystick8.c:1814: Test failed: 0x500: state[2]: got rgbButtons[1] 0 joystick8.c:1822: Test failed: 0x500: state[2]: WaitForSingleObject failed joystick8.c:1802: Test failed: 0x500: state[3]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[3]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[3]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[3]: got lZ 32767 joystick8.c:1802: Test failed: 0x500: state[4]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[4]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[4]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[4]: got lZ 32767 joystick8.c:1822: Test failed: 0x500: state[4]: WaitForSingleObject failed joystick8.c:1802: Test failed: 0x500: state[5]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[5]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[5]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[5]: got lZ 32767 joystick8.c:1813: Test failed: 0x500: state[5]: got rgbButtons[0] 0 joystick8.c:1814: Test failed: 0x500: state[5]: got rgbButtons[1] 0 joystick8.c:1822: Test failed: 0x500: state[5]: WaitForSingleObject failed joystick8.c:1828: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1830: Test failed: 0x500: state[6]: got lX 20779 joystick8.c:1831: Test failed: 0x500: state[6]: got lY 20779 joystick8.c:1832: Test failed: 0x500: state[6]: got lZ 32767 joystick8.c:1834: Test failed: 0x500: state[6]: got rgdwPOV[0] -1 joystick8.c:1836: Test failed: 0x500: state[6]: got rgbButtons[0] 0 joystick8.c:1853: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1856: Test failed: 0x500: state[6]: got lX 20779 joystick8.c:1857: Test failed: 0x500: state[6]: got lY 20779 joystick8.c:1858: Test failed: 0x500: state[6]: got lZ 32767 joystick8.c:1870: Test failed: 0x500: WaitForSingleObject failed joystick8.c:1873: Test failed: 0x500: Unacquire returned: 0x1 joystick8.c:1957: Test failed: 0x500: state[0]: got rgdwPOV[0] -1 joystick8.c:1960: Test failed: 0x500: state[0]: got rgbButtons[1] 0x80 joystick8.c:1953: Test failed: 0x500: state[1]: got lY -25984 joystick8: Timeout

1 0

Re: [PATCH v3 4/5] win32u: Read rawinput device preparsed data using virtual memory.
by Marvin July 27, 2022

July 27, 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=119786 Your paranoid android. === debian11 (32 bit report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Arabic:Morocco report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit German report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit French report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Hebrew:Israel report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Hindi:India report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Japanese:Japan report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Chinese:China report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (64 bit WoW report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout

1 0