From 5c74fc767600f75cd6d53bdc5926962b75a614ae Mon Sep 17 00:00:00 2001 From: Jens Axboe Date: Tue, 22 Dec 2015 13:40:14 -0700 Subject: [PATCH] backend: continue on failed wait_for() check, not break If we have this job file: [a] [b] wait_for=a [c] wait_for=a [d] then we expect a/d to run together, then b/c after a is done. However, right now we break out of the job loop, so it acts like a stonewall. That means that a will run first, then b/c/d. That isn't correct. Signed-off-by: Jens Axboe --- backend.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend.c b/backend.c index edc0644a..bd94078a 100644 --- a/backend.c +++ b/backend.c @@ -2130,7 +2130,7 @@ reap: if (waitee_running(td)) { dprint(FD_PROCESS, "%s: waiting for %s\n", td->o.name, td->o.wait_for); - break; + continue; } init_disk_util(td); -- 2.25.1