sosreport
Replies: 4 comments 1 reply
-
|
I haven't found any downside to using |
Beta Was this translation helpful? Give feedback.
-
|
in fact, just realised we don't do stagetwo tests here in CI for older releases (focal & jammy), only the latest releases. So, we wouldn't have picked this up here either. I know this could incur extra costs and such, how would we feel about enabling stagetwo for all supported platforms? |
Beta Was this translation helpful? Give feedback.
-
The difference is 9 releases for stageone tests vs. 6 releases for stagetwo tests. Probably not a big deal but let us check it internally. In general, referring to image family and test always latest (plus latest minus one) seems a good "automation" approach. |
Beta Was this translation helpful? Give feedback.
-
|
We'll probably need to go check internally for this before we make any changes |
Beta Was this translation helpful? Give feedback.
-
|
It's a ways in the past, but I don't believe Fully onboard. |
Beta Was this translation helpful? Give feedback.
-
Is there any reason why we stick to specific images rather than go with family name.
As part of fixing obfuscation issues in our recent upload to Ubuntu we also found the same issue with
msrload issue which avocado has picked up. Now, if we always had the latest images in Cirrus, we would have picked this up.I already did something similar for both
report_stageone_daily_taskandreport_stagetwo_daily_taskwhere I am using theimage_familyinstead ofimage_name, and this always picks up the latest image.If we did change to
image_family, we won't need to change thecirrus.ymlon a regular basis. The only time I would change, is when we have a new release which is every 6 months .Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions