Commit c99fb916 authored by Sebastien Robin's avatar Sebastien Robin

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

parent 2baf3b1e
...@@ -34,7 +34,7 @@ import signal ...@@ -34,7 +34,7 @@ import signal
import sys import sys
import time import time
MAX_TIMEOUT = 36000 MAX_TIMEOUT = 3600 * 4
class SubprocessError(EnvironmentError): class SubprocessError(EnvironmentError):
def __init__(self, status_dict): def __init__(self, status_dict):
......
  • @seb I noticed this case in one of our tests:

    redraft

    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:

    redraft2

    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.

Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment