erp5testnode: make the timeout shorter to avoid long wait time doing nothing

erp5/util/testnode/ProcessManager.py

@@ -34,7 +34,7 @@ import signal
 import sys
 import time
 
-MAX_TIMEOUT = 36000
+MAX_TIMEOUT = 3600 * 4
 
 class SubprocessError(EnvironmentError):
   def __init__(self, status_dict):

[Georgios Dagkakis]

@seb I noticed this case in one of our tests:

So if I understand correctly, the test is redrafted by the Test Result code where the timeout is set to 3 hours. Then it gets restarted, but it was still running in background, so it finishes as long as it did not reach the 4 hours timeout.

In other case where we get failure in the end:

We have

• Test Suite being redrafted by the 3 hours timeout of TestResult_restartStuckLine
• Then restarted, but being again redrafted a bit more than 4 hours than initial start, by the timeout of ProcessManager here
• Then restarted, but being again redrafted after the last timeout of TestResult_restartStuckLine

Is my reading correct? I think this makes it more possible that if the 4 hours timeout is reached once, then we will get new timeouts.