Cascading test failures

Greg Geldorp ggeldorp at
Fri Jul 16 08:51:23 CDT 2010

> From: Hans Leidekker [mailto:hans at]
> On Fri, 2010-07-16 at 15:12 +0200, Paul Vriens wrote:
> > In the past we have seen that on slower machines the number of tests
> > just exceeded the timeout. That has been 'corrected' back than by making
> > some tests interactive. I guess because of the multitude of new tests we
> > have ended up in the same situation.
> The msi:install test completes in 90 seconds here in a vm, so well
> within the timeout of 300 seconds.

The winetest.exe timeout is 120 seconds, not 300 (TestBot uses 300). So 90
seconds isn't that far off from the timeout.
The MsiInstallProductA() call in test_delete_services() consistently took 30
seconds (25% of the available time) during my testing.


More information about the wine-devel mailing list