Martin Pitt 5209e9afd2 tests: use less aggressive systemctl --wait timeout in TEST-03-JOBS (#4606) ... If the "systemctl start" happens at an "unlucky" time such as 1000.9 seconds and then e. g. runs for 2.6 s (sleep 2 plus the overhead of starting the unit and waiting for it) the END_SEC would be 1003.5s which would round to 1004, making the difference 4. On busier testbeds the overhead apparently can take a bit more than 0.5s. The main point is really that it doesn't wait that much longer, so "-le 4" seems perfectly fine. We allow up to 1.5s in the subsequent "wait5fail" test below too. Fixes #4582		2016-11-07 21:51:20 +03:00
..
Makefile	test: add test for jobs	2013-01-25 22:29:56 +01:00
test-jobs.sh	tests: use less aggressive systemctl --wait timeout in TEST-03-JOBS (#4606)	2016-11-07 21:51:20 +03:00
test.sh	test: merge check_nspawn() into run_nspawn()	2016-06-24 16:23:39 +02:00