diff options
| author | David Spickett <david.spickett@linaro.org> | 2020-05-15 15:43:39 +0100 |
|---|---|---|
| committer | David Spickett <david.spickett@linaro.org> | 2020-05-15 15:51:47 +0100 |
| commit | 765d89c2116e1338bb3e2e9df66f0a4dda464b9e (patch) | |
| tree | 87dda4e8e2b9b51ab0c9c22a2131215e808cd9eb | |
| parent | e83c1921ab640bb8ebb1ea6759dd8b0ed976b868 (diff) | |
jenkins-helpers.sh: Clarify HANDLING failure message
When a step fails and we carry on you get this:
RUNNING <step>
CARRYING ON after failure in <step>
HANDLING previous failure in <step2>
RUNNING <step2>
Which in context can be read to mean that <step> failed
then <step2> *also* failed. (especially if you don't know
to expect another RUN message)
Now we'll see:
HANDLING <step2> will handle previous failure
RUNNING <step2>
Change-Id: I52da2ce8ea976524f366fb590c230303f027c644
| -rw-r--r-- | jenkins-helpers.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/jenkins-helpers.sh b/jenkins-helpers.sh index 613f948f..32050ee1 100644 --- a/jenkins-helpers.sh +++ b/jenkins-helpers.sh @@ -1247,7 +1247,7 @@ run_step () skip=true ;; *:reset_on_fail) - echo "HANDLING previous failure in ${step[*]}" + echo "HANDLING ${step[*]} will handle previous failure" ;; *) assert false |