[PATCH 3/3] ddraw/tests: Add a IDirect3DDevice2 GetCaps test
Stefan Dösinger
stefan at codeweavers.com
Thu Dec 1 09:47:32 CST 2011
Am Donnerstag, 1. Dezember 2011, 15:15:23 schrieb Henri Verbeet:
> If we're going to redo the way the tests work anyway, we probably
> shouldn't reuse the same objects for everything either.
You mean reinitialize ddraw/d3d for every test? I'm not sure if that's a good
idea(or enough, depending on how you look at it). At least one of my Windows
machine(The radeon X1600 one) has occasional test failures in the ddraw visual
tests that occur right after d3d7 has been unloaded and d3d1 started. I
suspect it is a race condition somewhere in the d3d init and shutdown
functions(All I see is that the problems go away if I don't run the d3d7 tests
first).
Maybe spawning a new process for every test would work. I'm not sure if we can
or want to do that. In either case we don't want to use fullscreen mode if we
reinitialize d3d for every test. That's an issue for the visual tests, the d3d
ones are windowed anyway(Except those that explicitly test mode switches)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20111201/e915d933/attachment.pgp>
More information about the wine-devel
mailing list