If the test script exits nonzero but after setting the step status to
'fail', we can leave it that way. This is particularly relevant if
the iffail in the job spec says 'broken' or something. After this
change, a step can decide to override that.
An alternative would be to have the step script exit zero, but of
course that would (generally) leave the job to continue running more
steps!
Signed-off-by: Ian Jackson <i...@xenproject.org>
---
tcl/JobDB-Executive.tcl | 1 +
1 file changed, 1 insertion(+)
diff --git a/tcl/JobDB-Executive.tcl b/tcl/JobDB-Executive.tcl
index 4fe85696..38248823 100644
--- a/tcl/JobDB-Executive.tcl
+++ b/tcl/JobDB-Executive.tcl
@@ -325,6 +325,7 @@ proc step-set-status {flight job stepno st} {
AND status<>'aborted'
AND status<>'broken'
AND status<>'starved'
+ AND status<>'fail'
"
set pause 0
db-execute-array stopinfo "
--
2.20.1
