Description of problem: In Virt QE team, usually in them daily test, 1 task is 1 case. If a task failed but not a bug, they want to waive it. From now in job page, user only can waive recipe not task. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Submit a job with many tasks. 2. 3. Actual results: User can't waive task. Expected results: Customer in VirtQE team want to waive task. Additional info:
This was explicitly a deferred feature [1] in the 23.0 job page improvements, mainly because it requires some improvements to the job matrix as well and we weren't going to tackle that right now. https://beaker-project.org/dev/proposals/job-page-improvements.html#deferred-features
I have a few unclear questions. a) If a recipe set is marked as waived, should the recipe tasks and results within this recipe be marked as waived? b) If a recipe task is marked as waived, should the results within this task be marked as waived? c) If a is true, would unwaiving all the child recipes affect the parent recipe set? same for unwaiving all the results in a recipe task? Regardless of above questions, I have come out a Web UI for this. Here are the related patches: https://gerrit.beaker-project.org/#/c/4954/ record recipe task and result activities https://gerrit.beaker-project.org/#/c/4955/1 UI for waiving individual tasks/results
*** Bug 994422 has been marked as a duplicate of this bug. ***
At this point, whole redesign of Job Matrix is more likely than implementing this feature. We will take into a consideration when designing the Job Matrix page, but right now, this won't be worked on.