coordination #41057
opencoordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA
[epic] Make reviewing results easier
33%
Description
Observation¶
openQA test in scenario opensuse-15.1-DVD-x86_64-update_Leap_15.0_gnome@64bit fails in
gnucash
So I was just staring at this gnucash failure without any hint what went wrong. So what I had to do is
- to go to the previous results
- observe that the last run was green
- click on the last run and manually navigate to gnucash
- have two browser windows open to visually compare the difference
- see that gnucash seems to behave the same but still fails. Maybe some subtle font change somewhere?
- look at the source code trying to understand what the test does
- can't understand why the code didn't look for a needle. wondering if the code I am looking at is what actually ran
- open a terminal to look at the git history of gnucash.pm
- see that okurz reverted a previous change earlier today
- restart all tests that use gnucash
I think there are opportunities to reduce the amount of manual steps involved, for example
- tell me that the previous run was good and provide a link I can click on to compare, jump to the relevant test/needle right away
- warn me that the code I am looking at is not what was run. provide link to show the diff
Bonus points
- show links/diffs to other runs in the same build that also have gnucash failures to proof it's always the same
- links/diffs to gnucash failures in other job groups. I suppose in this case the problem was spotted in TW already
- single click solution to restart all affected tests at once
Updated by lnussel over 6 years ago
- Project changed from openQA Tests (public) to openQA Project (public)
- Description updated (diff)
- Category changed from Bugs in existing tests to 124
Updated by coolo over 6 years ago
- Subject changed from test fails in gnucash to Make reviewing results easier
Updated by coolo over 6 years ago
- Subject changed from Make reviewing results easier to [EPIC] Make reviewing results easier
- Difficulty set to hard
Updated by okurz about 5 years ago
- Related to coordination #19720: [epic] Simplify investigation of job failures added
Updated by okurz almost 5 years ago
- Subject changed from [EPIC] Make reviewing results easier to [epic] Make reviewing results easier
Updated by okurz over 4 years ago
- Status changed from New to Blocked
- Assignee set to okurz
- Target version set to Ready
waiting for results of #19720 first
Updated by szarate about 4 years ago
- Tracker changed from action to coordination
- Status changed from Blocked to New
- Difficulty deleted (
hard)
Updated by szarate about 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
Updated by okurz about 4 years ago
- Status changed from New to Blocked
- Difficulty set to hard
Updated by livdywan over 3 years ago
Can you confirm what this was blocking on? I see no reference and the subtask is in Future.
Updated by okurz over 3 years ago
In #41057#note-7 I made the statement that we should have #19720 first before continuing. It's the related issue that is also in "Ready". The subtask is in future, true.
Updated by livdywan over 3 years ago
- Related to deleted (coordination #19720: [epic] Simplify investigation of job failures)
Updated by livdywan over 3 years ago
- Blocked by coordination #19720: [epic] Simplify investigation of job failures added
Updated by okurz almost 3 years ago
- Status changed from Blocked to New
- Assignee deleted (
okurz) - Target version changed from Ready to future
both parent and child tickets are not currently on the backlog, need to unschedule for now