action #151399
closed
coordination #102915: [saga][epic] Automated classification of failures
QA (public) - coordination #94105: [epic] Use feedback from openqa-investigate to automatically inform on github pull requests, open tickets, weed out automatically failed tests
Identify reproducible *infrastructure* issues using openqa-investigate size:M
Added by okurz about 1 year ago.
Updated 8 months ago.
Category:
Feature requests
Description
Motivation¶
With #109920 openqa-investigate can identify clear PRODUCT REGRESSIONS and with #132272 we identify TEST REGRESSIONS. We can extend that same concept to now clearly identify infrastructure regressions and inform us about it
Acceptance criteria¶
- AC1: On failed openQA jobs with openqa-investigate info "S0: retry X, last_good_test X, last_good_build X, last_good_test+build X" (X: failed, V: passed) a comment is written pointing to a likely infrastructure regression
- AC2: No such comment is written on other jobs
Suggestions¶
- Copied from action #132272: Identify reproducible *TEST* issues (not product issues anymore) using openqa-investigate size:M added
- Description updated (diff)
- Copied to action #151402: [spike solution][timeboxed:20h] Allow to search for tests by comment on the UI size:M added
- Target version changed from Tools - Next to Ready
- Subject changed from Identify reproducible *infrastructure* issues using openqa-investigate size:M to Identify reproducible *infrastructure* issues using openqa-investigate
- Copied to action #152851: Notify about reproducible *infrastructure* issues using openqa-investigate added
- Subject changed from Identify reproducible *infrastructure* issues using openqa-investigate to Identify reproducible *infrastructure* issues using openqa-investigate size:M
- Description updated (diff)
- Status changed from New to Workable
- Copied to action #152853: Prevent faulty openQA workers causing wrong openqa-investigate conclusions size:M added
This was flaged due to the SLO. Brought it up on workadventu.re and there's no further questions.
- Priority changed from Normal to High
- Status changed from Workable to In Progress
- Assignee set to tinita
- Due date set to 2024-03-07
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
I found the new comment several times on osd. gru journals look ok.
- Due date deleted (
2024-03-07)
Also available in: Atom
PDF