Timeout is too low for Older / Slow machine which causes to test failure
MDAlFattah opened this issue · 1 comments
MDAlFattah commented
Issue:
After running the test.py script on my older and slightly slow machine and get failed because of timeout is less than my machine needed.
Log (from the console):
exitcode = arangosh_run.wait(timeout=30)
File "/home/fattah/.local/lib/python3.7/site-packages/psutil/__init__.py", line 1362, in wait
ret = super(Popen, self).wait(timeout)
File "/home/fattah/.local/lib/python3.7/site-packages/psutil/__init__.py", line 1275, in wait
return self._proc.wait(timeout)
File "/home/fattah/.local/lib/python3.7/site-packages/psutil/_pslinux.py", line 1516, in wrapper
return fun(self, *args, **kwargs)
File "/home/fattah/.local/lib/python3.7/site-packages/psutil/_pslinux.py", line 1724, in wait
return _psposix.wait_pid(self.pid, timeout, self._name)
File "/home/fattah/.local/lib/python3.7/site-packages/psutil/_psposix.py", line 98, in wait_pid
delay = check_timeout(delay)
File "/home/fattah/.local/lib/python3.7/site-packages/psutil/_psposix.py", line 64, in check_timeout
raise TimeoutExpired(timeout, pid=pid, name=proc_name)
psutil.TimeoutExpired: psutil.TimeoutExpired timeout after 30 seconds (pid=5152)
Solution:
- Go to \release-test-automation\release_tester\arangodb and open the sh.py script.
- On line 56 change
exitcode = arangosh_run.wait(timeout=100)
instead ofexitcode = arangosh_run.wait(timeout=30)
will solve the issue.
dothebart commented
make_data is now ran with async i/o with dynamic timeout and progress feedback.