From: Alexandre Julliard
> of course the testbot having a 5 minutes timeout makes this worse
Yeah, I don't remember the reasoning behind that choice. It probably makes more
sense
to use the same timeout as winetest.
Thanks for making your position clear before I spent time on implementing
stuff,
Greg Geldorp writes:
>> From: Alexandre Julliard
>>
>> I think it would be better to make the test detect such an environment
>> and have it skip some things if it finds that it's taking too long.
>
> I guess that's what we currently have... In effect, if it takes too long,
> the final tests are
> From: Alexandre Julliard
>
> I think it would be better to make the test detect such an environment
> and have it skip some things if it finds that it's taking too long.
I guess that's what we currently have... In effect, if it takes too long,
the final tests are skipped. I was hoping we could d
Greg Geldorp writes:
> Although the number of timeouts in msi tests has dropped considerably after
> Hans decided to do something about them, they're unfortunately not
> completely gone. It seems that the remaining timeouts have a strong
> dependency on the environment. It's possible to tweak the
On Wed, 2011-01-05 at 14:01 +0100, wy...@volny.cz wrote:
> s there is an activity to make (not only) WylBOT green and happy
> ;c) i can add more info, based on WyldBOT's install documentation i
> looked right now and found there:
>
> * Turn off system restore
>
> So longer time out may not help
