action #120858
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Configure all PowerVM test suite to use `START_AFTER_TEST` with some chosen basic PowerVM test suite per flavor
Description
Motivation¶
As PowerVM infrastructure is not stable at the moment let's show less failures in our dashboard and more unscheduled jobs, anyway this is reported to RMs in confluence for each milestone acceptance report. The final goal is to make as robust as possible the YaST job group, regardless of infra issues.
Acceptance criteria¶
AC1: Configure all PowerVM test suite to use START_AFTER_TEST with some chosen basic PowerVM test suite per flavor
Additional information¶
- Notice that this not solve the problem as the failure is sporadic, so it might be that those 2 test suites chosen would be green and schedule the rest, but according to last build, there are less changes as mostly all was failed for PowerVM.
- afir we cannot link from different flavors, so for Full we will link to the most basic one
skip_registrationand for Online toguided_btrfs.
Updated by JERiveraMoya over 1 year ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
Updated by zoecao over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to zoecao
Updated by zoecao over 1 year ago
Submit MR for this ticket:
MR: https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/439
I didn't add the 'START_AFTER_TEST' to "all" of the powerVM cases, for the passed cases, I skipped, otherwise these stable cases can not run if case 'guided_btrfs' is failed.
And I also checked the powerVM cases' previous results, I also skipped the following cases, because I think based on history results, these cases may pass with more then 50% opportunity:
sles+sdk+proxy_SCC_via_YaST_ncurses: https://openqa.suse.de/tests/9968098#next_previous
msdos: https://openqa.suse.de/tests/9969411#next_previous
textmode: https://openqa.suse.de/tests/9969427#next_previous
yast_no_self_update: https://openqa.suse.de/tests/9969423#next_previous
Feel free to leave comments if need to add the setting for the cases above.
Updated by JERiveraMoya over 1 year ago
zoecao wrote:
Submit MR for this ticket:
MR: https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/439
I didn't add the 'START_AFTER_TEST' to "all" of the powerVM cases, for the passed cases, I skipped, otherwise these stable cases can not run if case 'guided_btrfs' is failed.
And I also checked the powerVM cases' previous results, I also skipped the following cases, because I think based on history results, these cases may pass with more then 50% opportunity:
sles+sdk+proxy_SCC_via_YaST_ncurses: https://openqa.suse.de/tests/9968098#next_previous
msdos: https://openqa.suse.de/tests/9969411#next_previous
textmode: https://openqa.suse.de/tests/9969427#next_previous
yast_no_self_update: https://openqa.suse.de/tests/9969423#next_previousFeel free to leave comments if need to add the setting for the cases above.
The situation is too random and too annoying to review to do any exception IMO, my plan is to move to development job group all those test suites except one if things do not get better in next milestone for example.
Updated by zoecao over 1 year ago
- Status changed from In Progress to Resolved
MR is merged, close here, thanks.