Re: [1/5] msi/tests: Use a different product code in the package tests to avoid cascading test failures.

2010-08-27 Thread testbot
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=4818 Your paranoid android.

Re: Cascading test failures

2010-07-16 Thread Jeff Zaroyko
On Fri, Jul 16, 2010 at 11:35 PM, Hans Leidekker wrote: > 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 b

RE: Cascading test failures

2010-07-16 Thread Greg Geldorp
> From: Hans Leidekker [mailto:h...@meelstraat.net] > > 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 b

Re: Cascading test failures

2010-07-16 Thread Alexandre Julliard
Hans Leidekker writes: > On Fri, 2010-07-16 at 04:36 -0700, Greg Geldorp wrote: > >> For all the cases I've checked, when these 1574 errors occur the preceding >> msi:install test timed out (the reverse is not true, I see msi:install >> timeouts followed by a successful msi:package). > > Do y

Re: Cascading test failures

2010-07-16 Thread Hans Leidekker
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 t

Re: Cascading test failures

2010-07-16 Thread Paul Vriens
On 07/16/2010 03:05 PM, Hans Leidekker wrote: On Fri, 2010-07-16 at 04:36 -0700, Greg Geldorp wrote: For all the cases I've checked, when these 1574 errors occur the preceding msi:install test timed out (the reverse is not true, I see msi:install timeouts followed by a successful msi:pack

Re: Cascading test failures

2010-07-16 Thread Hans Leidekker
On Fri, 2010-07-16 at 04:36 -0700, Greg Geldorp wrote: > For all the cases I've checked, when these 1574 errors occur the preceding > msi:install test timed out (the reverse is not true, I see msi:install > timeouts followed by a successful msi:package). Do you have any clue why the test time

Cascading test failures

2010-07-16 Thread Greg Geldorp
Ideally, tests should be independent on each other. That's not the case right now. A clear example is msi:package, which often fails (on XP) with 1574 errors, see http://test.winehq.org/data/tests/msi:package.html. For all the cases I've checked, when these 1574 errors occur the preceding msi:in