Enumeration of devices was checked in real boxes and device was enumerated once at least: windows 10, windows 8, windows XP and windows98. The last one is worth of checking I think, since old interfaces were used in this old windows only. And some games work only in this box.
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=58622
Your paranoid android.
=== w1064v1809_he (32 bit report) ===
ddraw: ddraw1.c:11061: Test failed: Got unexpected color 0x00ffffff.
=== wvistau64 (64 bit report) ===
ddraw: ddraw1.c:13162: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw1.c:13162: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw1.c:13162: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw1.c:13162: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw1.c:13162: Test failed: Failed to get d3d1 interface, hr 0x80004002.
=== wvistau64 (64 bit report) ===
ddraw: ddraw2.c:14046: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw2.c:14046: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw2.c:14046: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw2.c:14046: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw2.c:14046: Test failed: Failed to get d3d2 interface, hr 0x80004002.
=== wvistau64 (64 bit report) ===
ddraw: ddraw4.c:16601: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw4.c:16601: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw4.c:16601: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw4.c:16601: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw4.c:16601: Test failed: Failed to get d3d3 interface, hr 0x80004002.
=== w1064v1809 (32 bit report) ===
ddraw: 1a90:ddraw7: unhandled exception c0000005 at 738340F8
=== w1064v1809_2scr (32 bit report) ===
ddraw: 1b88:ddraw7: unhandled exception c0000005 at 73A340F8
=== w1064v1809_ar (32 bit report) ===
ddraw: 1ac4:ddraw7: unhandled exception c0000005 at 72CE40F8
=== w1064v1809_he (32 bit report) ===
ddraw: 1aa8:ddraw7: unhandled exception c0000005 at 734F40F8
=== w1064v1809_ja (32 bit report) ===
ddraw: 1b44:ddraw7: unhandled exception c0000005 at 723740F8
=== w1064v1809_zh_CN (32 bit report) ===
ddraw: 1b54:ddraw7: unhandled exception c0000005 at 734240F8
=== wvistau64 (64 bit report) ===
ddraw: ddraw7.c:16572: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w2008s64 (64 bit report) ===
ddraw: ddraw7.c:16572: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w864 (64 bit report) ===
ddraw: ddraw7.c:16572: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w1064v1507 (64 bit report) ===
ddraw: ddraw7.c:16572: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== w1064v1809 (64 bit report) ===
ddraw: ddraw7.c:16572: Test failed: Failed to get d3d7 interface, hr 0x80004002.
=== debian10 (32 bit report) ===
ddraw: ddraw2.c:13994: Test failed: Test 1, wrong device name ddraw2.c:14088: Test failed: Got '~' and 'Direct3D HEL' ddraw2.c:14088: Test failed: Got '~' and 'Direct3D HAL' ddraw4.c:16549: Test failed: Test 1, wrong device name ddraw4.c:16643: Test failed: Got '~' and 'Direct3D HEL' ddraw4.c:16643: Test failed: Got '~' and 'Direct3D HAL'
=== debian10 (32 bit French report) ===
ddraw: ddraw2.c:13994: Test failed: Test 1, wrong device name ddraw2.c:14088: Test failed: Got '®~' and 'Direct3D HEL' ddraw2.c:14088: Test failed: Got '®~' and 'Direct3D HAL' ddraw4.c:16549: Test failed: Test 1, wrong device name ddraw4.c:16643: Test failed: Got '®~' and 'Direct3D HEL' ddraw4.c:16643: Test failed: Got '®~' and 'Direct3D HAL'
=== debian10 (32 bit Japanese:Japan report) ===
ddraw: ddraw2.c:13994: Test failed: Test 1, wrong device name ddraw2.c:14088: Test failed: Got '®~' and 'Direct3D HEL' ddraw2.c:14088: Test failed: Got '®~' and 'Direct3D HAL' ddraw4.c:16549: Test failed: Test 1, wrong device name ddraw4.c:16643: Test failed: Got '®~' and 'Direct3D HEL' ddraw4.c:16643: Test failed: Got '®~' and 'Direct3D HAL'
=== debian10 (32 bit Chinese:China report) ===
ddraw: ddraw2.c:13994: Test failed: Test 1, wrong device name ddraw2.c:14088: Test failed: Got '®~' and 'Direct3D HEL' ddraw2.c:14088: Test failed: Got '®~' and 'Direct3D HAL' ddraw4.c:16549: Test failed: Test 1, wrong device name ddraw4.c:16643: Test failed: Got '®~' and 'Direct3D HEL' ddraw4.c:16643: Test failed: Got '®~' and 'Direct3D HAL'
=== debian10 (32 bit WoW report) ===
ddraw: ddraw2.c:13994: Test failed: Test 1, wrong device name ddraw2.c:14088: Test failed: Got '~' and 'Direct3D HEL' ddraw2.c:14088: Test failed: Got '~' and 'Direct3D HAL' ddraw4.c:16549: Test failed: Test 1, wrong device name ddraw4.c:16643: Test failed: Got '~' and 'Direct3D HEL' ddraw4.c:16643: Test failed: Got '~' and 'Direct3D HAL'
=== debian10 (64 bit WoW report) ===
ddraw: ddraw2.c:13994: Test failed: Test 1, wrong device name ddraw2.c:14088: Test failed: Got '~' and 'Direct3D HEL' ddraw2.c:14088: Test failed: Got '~' and 'Direct3D HAL' ddraw4.c:16549: Test failed: Test 1, wrong device name ddraw4.c:16643: Test failed: Got '~' and 'Direct3D HEL' ddraw4.c:16643: Test failed: Got '~' and 'Direct3D HAL'
-
David Adam -
Marvin