action #46598
closedTest results from SLE12SP4 milestones are gone
0%
Description
Observation¶
[24/01/2019 08:57:12] <mgriessmeier> okurz: did I miss something? or did we lose a lot of 12SP4 GM jobs?
[24/01/2019 09:25:48] <okurz> mgriessmeier: yes, a lot of test results are gone. 12SP3 is still there: https://openqa.suse.de/group_overview/55?only_tagged=1
[24/01/2019 09:26:08] <okurz> mgriessmeier: can you report that and escalate? And mention "backup&recovery" ;)
[24/01/2019 10:09:55] <okurz> mgriessmeier: ok, I reported that to RM+PrjM. coolo stated the results were gone for longer already and it might be related to tagging in the parent job group
Updated by coolo over 5 years ago
- Priority changed from High to Urgent
- Target version set to Current Sprint
- Difficulty set to easy
JobGroups::important_builds is only considering this job group's comments. With SP4 the tagging moved to the parent group and JobGroups::tags and as such you see the tags, but they don't matter - and we happily deleted all tagged results soon afterwards.
This is a very unfortunate oversight
Updated by mkittler over 5 years ago
Can you point to the exact job group which is affected?
But according to @coolo's description this even looks like a user mistake? Or what exactly should be improved from the openQA-side?
Updated by coolo over 5 years ago
You misunderstood me there - I was trying to give the engineer picking it up a headstart :)
The expectation is: if the parent group has a build tagged as important, the tag is displayed in the job group and that build is important while deleting.
Updated by mkittler over 5 years ago
- Assignee set to mkittler
Ok, so I'll make the tag inheritance not only affect the dashboard but also the cleanup algorithm.
Updated by mkittler over 5 years ago
- Status changed from New to In Progress