Commit eb77cb53 authored by Jérome Perrin's avatar Jérome Perrin

ProcessingNodeTestCase.tic: increase delay to 30 minutes

Now that we fail immediately in case of failure, the deadline can be
safely increased, because it only protects against kind of infinite loops.

Increasing the delay should fix RuntimeError: tic is looping forever
errors with only messages in status -1, that we sometimes saw on testnodes.
parent b59999ad
Pipeline #19641 failed with stage
...@@ -269,7 +269,7 @@ class ProcessingNodeTestCase(ZopeTestCase.TestCase): ...@@ -269,7 +269,7 @@ class ProcessingNodeTestCase(ZopeTestCase.TestCase):
transaction.commit() transaction.commit()
self.abort() self.abort()
def tic(self, verbose=0, stop_condition=lambda message_list: False, delay=10*60): def tic(self, verbose=0, stop_condition=lambda message_list: False, delay=30*60):
"""Execute pending activities. """Execute pending activities.
This method executes activities until all messages are executed successfully, This method executes activities until all messages are executed successfully,
...@@ -281,7 +281,7 @@ class ProcessingNodeTestCase(ZopeTestCase.TestCase): ...@@ -281,7 +281,7 @@ class ProcessingNodeTestCase(ZopeTestCase.TestCase):
to continue. to continue.
If the total time spent processing activities exceeded `delay` seconds (default If the total time spent processing activities exceeded `delay` seconds (default
10 minutes), then the processing is interrupted and `tic` raise a RuntimeError 30 minutes), then the processing is interrupted and `tic` raise a RuntimeError
exception. exception.
""" """
transaction.commit() transaction.commit()
......
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