Description of problem: I guess the overall job status should not be "Completed" if there are recipes which were aborted or cancelled. Perhaps the "worst" status from contained recipes should be used here? Version-Release number of selected component (if applicable): 0.6.13 Steps to Reproduce: https://beaker.engineering.redhat.com/jobs/92248
This is by design. We show the "most severe" result (Panic > Fail > Warn > Pass) but the "least severe" status. That way, if one recipe is Running but another is still Queued, the overall status will show Queued. I think if we only had status Finished, it would make sense as ist. The problem is that we have three finished statuses: Cancelled, Aborted, and Completed. Which is kind of expressing a result, as well as a status, but that's what we have...
On second thought, I suppose there is no reason we couldn't change the "severity" such that Aborted < Cancelled < Completed ("severity" is surely the wrong word to use here), apart from the fact that it would change the behaviour which might surprise people.
I was thinking about this again. I think it is worth changing the status calculations so that Aborted < Cancelled < Completed (where lower status "wins"). In other words, a recipe with some Completed tasks and some Aborted would be Aborted, not Completed as it is now. Similarly, a recipe with some Completed tasks and some Cancelled would be Cancelled, not Completed as it is now. The current behaviour is very counter-intuitive and not really useful for This would handily also fix bug 1195558. This would be a backwards incompatible change but I don't think there is anything we can do about it aside from adding a release note to draw people's attention to it.
+1 I think this would be a good change.
http://gerrit.beaker-project.org/4189
*** Bug 1217472 has been marked as a duplicate of this bug. ***
Beaker 21.0 has been released.
*** Bug 616405 has been marked as a duplicate of this bug. ***