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=119863
Your paranoid android.
=== w10pro64_zh_CN (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
=== w7u_adm (32 bit report) ===
mshtml:
script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658941745587 expected 1658941745649"
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
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
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
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
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
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
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
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
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
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=119780
Your paranoid android.
=== debian11 (32 bit report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (32 bit Arabic:Morocco report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (32 bit German report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (32 bit French report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (32 bit Hebrew:Israel report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (32 bit Hindi:India report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (32 bit Japanese:Japan report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (32 bit Chinese:China report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
=== debian11 (64 bit WoW report) ===
dinput:
joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2
joystick8.c:4333: Test failed: got path L""
joystick8.c:4339: Test failed: got error 3
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6
joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6
joystick8: Timeout
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=119771
Your paranoid android.
=== w10pro64_zh_CN (64 bit report) ===
ws2_32:
sock.c:12062: Test failed: got 1.
sock.c:12063: Test failed: got 0.
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=119769
Your paranoid android.
=== debian11 (32 bit report) ===
Report validation errors:
dxgi:dxgi crashed (c0000005)
=== debian11 (32 bit Chinese:China report) ===
Report validation errors:
dxgi:dxgi crashed (c0000005)
=== debian11 (32 bit WoW report) ===
Report validation errors:
dxgi:dxgi crashed (c0000005)
=== debian11 (64 bit WoW report) ===
dxgi:
Unhandled exception: page fault on write access to 0x0000003c00000320 in 64-bit code (0x000000712b01ba).
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=119768
Your paranoid android.
=== debian11 (32 bit report) ===
d3d8:
Unhandled exception: page fault on read access to 0x007b1000 in 32-bit code (0x714b857f).
=== debian11 (32 bit WoW report) ===
d3d8:
Unhandled exception: page fault on read access to 0x00112010 in 32-bit code (0x714b857f).
=== debian11 (64 bit WoW report) ===
d3d8:
device: Timeout
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=119767
Your paranoid android.
=== debian11 (32 bit report) ===
d3d8:
Unhandled exception: page fault on write access to 0x00001000 in 32-bit code (0x714b575e).
Report validation errors:
dxgi:dxgi crashed (c0000005)
=== debian11 (32 bit Chinese:China report) ===
Report validation errors:
dxgi:dxgi crashed (c0000005)
=== debian11 (32 bit WoW report) ===
d3d8:
Unhandled exception: page fault on write access to 0x00260030 in 32-bit code (0x714b575e).
Report validation errors:
dxgi:dxgi crashed (c0000005)
=== debian11 (64 bit WoW report) ===
d3d8:
device: Timeout
d3d9:
Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000000712b2dae).
dxgi:
Unhandled exception: page fault on write access to 0x0000000100000001 in 64-bit code (0x000000712b01ba).
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=119735
Your paranoid android.
=== w7u_2qxl (32 bit report) ===
mshtml:
script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658854080136 expected 1658854080198"
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=119734
Your paranoid android.
=== w8 (32 bit report) ===
mshtml:
htmldoc.c:2648: Test failed: unexpected call GetOverrideKeyPath
htmldoc.c:2648: Test failed: unexpected call GetOverrideKeyPath
htmldoc: Timeout
=== w1064_tsign (64 bit report) ===
mshtml:
htmldoc: Timeout
=== w10pro64 (32 bit report) ===
mshtml:
script.c:3119: Test failed: ReportResult failed: 80ef0001
=== w864 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
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=119732
Your paranoid android.
=== w10pro64 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
=== w8 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
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=119731
Your paranoid android.
=== w1064 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
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=119730
Your paranoid android.
=== w10pro64_ar (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
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=119729
Your paranoid android.
=== w1064 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
=== w1064v1809 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
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=119740
Your paranoid android.
=== w1064v1507 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally