ci: Also run CI jobs on almalinux-9 - #5350
Conversation
Signed-off-by: Wolfgang Hoschek <wolfgang.hoschek@mac.com>
| - fedora.yaml | ||
| - archlinux.yaml | ||
| - opensuse.yaml | ||
| - almalinux-9.yaml |
There was a problem hiding this comment.
We only test Tier1 and Tier2 templates on the CI
https://lima-vm.io/docs/templates/
There was a problem hiding this comment.
If we are going to add almalinux-9, we have to consider:
- why not add almalinux-10
- why prefer alma over rocky
There was a problem hiding this comment.
Almalinux is a major mainstream distro, and a lot of folks are using it. Adding almalinux-10 and rocky too would be even better to gain confidence, sure :-)
There was a problem hiding this comment.
Due the flakiness of the CI, it is not realistic to cover both alma and rocky, and their multiple versions.
So we have to come up a reason why we should prioritize almalinux-9 over other ones.
There was a problem hiding this comment.
Personally, I'd prefer almalinux-10. The only reason I didn't include it in the PR is because it actually fails CI systematically (due to a real bug, not a flakiness issue).
There was a problem hiding this comment.
bug
Could you open an issue ?
AkihiroSuda
added
area/test
2 participants
What This PR Changes
Make sure AlmaLinux-9 (which is among the canned Lima templates) continues to work.
FYI, the analog change actually fails for AlmaLinux-10 but that's a separate issue with the Lima mDNS script and its missing
kernel-modules-extra-$(uname -r)dependency.How I Tested This
Passed the Lima Github CI matrix.