Hi,
While running your changed tests, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check?
Full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=58620
Your paranoid android.
=== wvistau64_fr (task log) ===
Task errors: The previous 1 run(s) terminated abnormally
=== wvistau64 (64 bit report) ===
ddraw: ddraw1.c:13151: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw1.c:13151: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw1.c:13151: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw1.c:13151: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw1.c:13151: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== wvistau64 (64 bit report) ===
ddraw: ddraw2.c:14035: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw2.c:14035: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw2.c:14035: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw2.c:14035: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw2.c:14035: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== wvistau64_fr (32 bit report) ===
Report errors: ddraw:ddraw4 has unaccounted for skip messages The report seems to have been truncated
=== wvistau64_fr (task log) ===
Task errors: An error occurred while waiting for the test to complete: network read timed out (wait2/connect:AgentVersion.h:0/9) The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died) The previous 2 run(s) terminated abnormally
=== wvistau64 (64 bit report) ===
ddraw: ddraw4.c:16590: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw4.c:16590: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw4.c:16590: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw4.c:16590: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw4.c:16590: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w1064v1809 (32 bit report) ===
ddraw: 1a68:ddraw7: unhandled exception c0000005 at 737440F8
=== w1064v1809_2scr (32 bit report) ===
ddraw: 1b30:ddraw7: unhandled exception c0000005 at 747B40F8
=== w1064v1809_ar (32 bit report) ===
ddraw: 1940:ddraw7: unhandled exception c0000005 at 72CB40F8
=== w1064v1809_he (32 bit report) ===
ddraw: 112c:ddraw7: unhandled exception c0000005 at 737C40F8
=== w1064v1809_ja (32 bit report) ===
ddraw: 1bd8:ddraw7: unhandled exception c0000005 at 723640F8
=== w1064v1809_zh_CN (32 bit report) ===
ddraw: 1b08:ddraw7: unhandled exception c0000005 at 734440F8
=== wvistau64 (64 bit report) ===
ddraw: ddraw7.c:16561: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw7.c:16561: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw7.c:16561: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw7.c:16561: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw7.c:16561: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== debian10 (32 bit report) ===
ddraw: ddraw2.c:13987: Test failed: Test 1, wrong device name ddraw2.c:14070: Test failed: Got '~' and 'Direct3D HEL' ddraw2.c:14070: Test failed: Got '~' and 'Direct3D HAL' ddraw4.c:16542: Test failed: Test 1, wrong device name ddraw4.c:16625: Test failed: Got '~' and 'Direct3D HEL' ddraw4.c:16625: Test failed: Got '~' and 'Direct3D HAL'
=== debian10 (32 bit French report) ===
ddraw: ddraw2.c:13987: Test failed: Test 1, wrong device name ddraw2.c:14070: Test failed: Got '®~' and 'Direct3D HEL' ddraw2.c:14070: Test failed: Got '®~' and 'Direct3D HAL' ddraw4.c:16542: Test failed: Test 1, wrong device name ddraw4.c:16625: Test failed: Got '®~' and 'Direct3D HEL' ddraw4.c:16625: Test failed: Got '®~' and 'Direct3D HAL'
=== debian10 (32 bit Japanese:Japan report) ===
ddraw: ddraw2.c:13987: Test failed: Test 1, wrong device name ddraw2.c:14070: Test failed: Got '®~' and 'Direct3D HEL' ddraw2.c:14070: Test failed: Got '®~' and 'Direct3D HAL' ddraw4.c:16542: Test failed: Test 1, wrong device name ddraw4.c:16625: Test failed: Got '®~' and 'Direct3D HEL' ddraw4.c:16625: Test failed: Got '®~' and 'Direct3D HAL'
=== debian10 (32 bit Chinese:China report) ===
ddraw: ddraw2.c:13987: Test failed: Test 1, wrong device name ddraw2.c:14070: Test failed: Got '®~' and 'Direct3D HEL' ddraw2.c:14070: Test failed: Got '®~' and 'Direct3D HAL' ddraw4.c:16542: Test failed: Test 1, wrong device name ddraw4.c:16625: Test failed: Got '®~' and 'Direct3D HEL' ddraw4.c:16625: Test failed: Got '®~' and 'Direct3D HAL'
=== debian10 (32 bit WoW report) ===
ddraw: ddraw2.c:13987: Test failed: Test 1, wrong device name ddraw2.c:14070: Test failed: Got '~' and 'Direct3D HEL' ddraw2.c:14070: Test failed: Got '~' and 'Direct3D HAL' ddraw4.c:16542: Test failed: Test 1, wrong device name ddraw4.c:16625: Test failed: Got '~' and 'Direct3D HEL' ddraw4.c:16625: Test failed: Got '~' and 'Direct3D HAL'
=== debian10 (64 bit WoW report) ===
ddraw: ddraw2.c:13987: Test failed: Test 1, wrong device name ddraw2.c:14070: Test failed: Got '~' and 'Direct3D HEL' ddraw2.c:14070: Test failed: Got '~' and 'Direct3D HAL' ddraw4.c:16542: Test failed: Test 1, wrong device name ddraw4.c:16625: Test failed: Got '~' and 'Direct3D HEL' ddraw4.c:16625: Test failed: Got '~' and 'Direct3D HAL'
-
David Adam -
Marvin