Wine Test Shell - timeouts during test runs too short?
stefan at codeweavers.com
Sun Jan 27 06:53:41 CST 2008
Am Sonntag, 27. Januar 2008 13:49:36 schrieb Reece Dunn:
> On 27/01/2008, Stefan Dösinger <stefan at codeweavers.com> wrote:
> > Am Sonntag, 27. Januar 2008 12:18:12 schrieb Reece Dunn:
> > > Hi,
> > >
> > > When running the Wine Test Shell to run the tests as part of
> > > http://test.winehq.org/, there are several timeouts in different
> > > places.
> > >
> > > These may be valid timeouts, but on my Vista test machine ddraw:d3d
> > > and msi:install generate the timeout message box part way through the
> > > test run, even though they continue and complete. Those tests are just
> > > slow.
> > If you don't have a 3D accelerator(e.g. running in a VM), the ddraw d3d
> > and visual tests will attempt to use the RGB software rendering device,
> > which *is* slow. Running the visual test takes a few minutes instead of a
> > few secounds.
> These are running on a decent spec Vista machine that is not running
> through VM.
> I don't know if 3D acceleration is on; it looks like it is off (the
> colour gradiant sweep tests take a while to flick through). This is
> strange though, because it is the default configuration for the Vista
> machine and games like Oblivion and Command and Conquer 3 play fine
> (but those are using D3D, not DDraw).
The ddraw "d3d" and "visual" tests use d3d - earliear d3d versions(d3d <= 7)
are a subset of ddraw.dll . It could be that your driver doesn't like
something about the way the test initializes d3d, so the test falls back to
the software renderer.
More information about the wine-devel