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
> 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
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
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
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
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
