Hi,
While running your changed tests on Windows, 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 http://testbot.winehq.org/JobDetails.pl?Key=10677
Your paranoid android.
=== WXPPROSP3 (32 bit device) === device: unhandled exception c0000005 at 0040320F
=== W2K3R2SESP2 (32 bit device) === device: unhandled exception c0000005 at 0040320F
=== WVISTAADM (32 bit device) === device: unhandled exception c0000005 at 0040320F
=== W2K8SE (32 bit device) === device: unhandled exception c0000005 at 0040320F
=== W7PRO (32 bit device) === device: unhandled exception c0000005 at 0040320F
=== W7PROX64 (32 bit device) === device: unhandled exception c0000005 at 0040320F
=== W7PROX64 (64 bit device) === Timeout
On 2 May 2011 13:24, Marvin testbot@testbot.winehq.org wrote:
=== WXPPROSP3 (32 bit device) === device: unhandled exception c0000005 at 0040320F
For what it's worth, not sure if you figured this out by yourself yet or not, but you need to handle create_device() failing to create a device on machines like the testbot that don't have D3D hardware.