test/cli/scheduler: make the test more robust against time effects It is perfectly possible that another task was scheduled just after the first one did finish. This used to show up on slower machines.
1 files changed, 2 insertions(+), 2 deletions(-) M tests/test_cli.py
M tests/test_cli.py +2 -2
@@ 548,9 548,9 @@ def test_scheduler(engine, cli, cleanup) tid = engine.execute('select id from rework.task').scalar() t = Task.byid(engine, tid) wait_true(lambda: t.status == 'done') - r = cli('list-tasks', engine.url) - assert scrub(r.output).strip() == ( + r = cli('list-tasks', engine.url) + assert scrub(r.output).strip().startswith( '<X> print_sleep_and_go_away done ' '[<X>-<X>-<X> <X>:<X>:<X>.<X>UTC] → ' '[<X>-<X>-<X> <X>:<X>:<X>.<X>UTC] → '