Force_result comment cannot be added on a cancelled child job size:M
I tried to add a force_result comment on a child job (with cancelled status) dependent on another job (with failed status) where a force_result comment had already been added:
Upon submitting the comment, I received an error pop-up saying
The comment couldn't be added: Bad Request (screenshot added).
I tried adding a regular comment and subsequently editing it to a force_result pattern. The regular comment could be added fine, but the edit did not go through, with the same error.
I do not have enough data to tell whether this is happening consistently. I had previously been able to add a force_result comment on dependent jobs, but cannot recall whether/how they were child-parent linked.
Steps to reproduce:
- Open https://openqa.suse.de/tests/10826620
- Add comment
One only gets the alert as mentioned in the description. The web dev tools reveal a better error message:
force_result only allowed on finished jobs
So this is supposedly simply because it is a cancelled job and not a "done" job (and has nothing to do with the child-relation).
It would be helpful to have a way to ignore cancelled jobs (for the purposes of qam-openqa review) as well, if it's technically possible. When a chained job fails and the linked jobs are cancelled as a result, it doesn't help to add a force_result on the failed job only; the cancelled jobs still block the approval.
- Category set to Feature requests
- Status changed from Feedback to New
- Assignee deleted (
- Priority changed from Normal to Low
- Target version changed from Ready to future
It is definitely technically possible. The question is just whether we want it. When @okurz introduced the feature he explicitly added those checks.
I think I only initially supported finished jobs as that is easier to support and has less implications. I guess by now we can extend to cover not finished jobs as well. One can have big impact with forcing results but now it's in the responsibility of the reviewers and fully traceable so I agree that we should add the support. But not right now due to backlog constraints.