Commit 75b39618 authored by Jérome Perrin's avatar Jérome Perrin

ui_test_core: do not sleep in Zuite_waitForActivities

Otherwise in the worst case we sleep for 1000 seconds.
parent 9d66a2e3
from time import sleep
def waitForActivities(self, count=1000): def waitForActivities(self, count=1000):
""" """
...@@ -15,7 +14,6 @@ def waitForActivities(self, count=1000): ...@@ -15,7 +14,6 @@ def waitForActivities(self, count=1000):
if all(x.processing_node == -2 for x in x): if all(x.processing_node == -2 for x in x):
break break
activity_tool.process_timer(None, None) activity_tool.process_timer(None, None)
sleep(1)
raise RuntimeError('tic is looping forever.') raise RuntimeError('tic is looping forever.')
def UpdateImage(image): def UpdateImage(image):
......
  • This is too aggressive if we have activities that are delayed. Besides activity errors (I admit we should not have any), code can for example use at_date to throttle execution for an interface (we do have this in a project); this may not be pertinent enough for UI tests. In non-UI tests, the clock is shifted by 45s every 10 iterations.

  • Thanks, that's a good point. Even though there was probably no ui test where it happens, there's no reason that this processing of activities does not shift the clock like in server side test version of tic I pushed a new commit implementing this.

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