The increased timeouts can be needed if the computer is otherwise busy (which should not be happening on the official TestBot unless the administrator is doing some maintenance on the side). The new timeouts should provide at least a 50% margin, thus also leaving some room for Wine to grow.
Signed-off-by: Francois Gouget fgouget@codeweavers.com ---
There was a timeout on the TestBot once during a Wine update. The same day I also got a timeout on my box (but that's less surprising since it may have been busy with other things at the time). Hopefully the timeout increases will prevent a reoccurrence.
testbot/lib/WineTestBot/Config.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/testbot/lib/WineTestBot/Config.pm b/testbot/lib/WineTestBot/Config.pm index a83085d44..157617780 100644 --- a/testbot/lib/WineTestBot/Config.pm +++ b/testbot/lib/WineTestBot/Config.pm @@ -95,13 +95,13 @@ $MaxTaskTries = 3; # Exe build timeouts (in seconds) # - For a full build $ExeBuildNativeTimeout = 60; -$ExeBuildTestTimeout = 2 * 60; +$ExeBuildTestTimeout = 4 * 60; # - For a single module $ExeModuleTimeout = 30;
# Wine build timeouts (in seconds) # - For a full build -$WineBuildTimeout = 20 * 60; +$WineBuildTimeout = 25 * 60; # - For a single module $WineModuleTimeout = 60;