New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
continuous integration: add kexec test cycle #243
Labels
Comments
+1 on having two separate tests one with and one without kexec. |
stapelberg
added a commit
that referenced
this issue
Jan 13, 2024
stapelberg
added a commit
to gokrazy/updater
that referenced
this issue
Jan 13, 2024
stapelberg
added a commit
to gokrazy/bakery
that referenced
this issue
Jan 13, 2024
stapelberg
changed the title
continuous integration test gap: skip kexec to exercise bootloader
continuous integration: add kexec test cycle
Jan 13, 2024
With the linked commits, kexec should now be skipped in CI. I re-titled the issue to track adding an explicit kexec test. Not terribly urgent, though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of rtr7/router7#83, I noticed that in our continuous integration setup, the MBR bootloader is not actually tested because we’re using kexec to reboot into new kernels on amd64. The result is that a broken bootloader does not block merging the offending change.
I think we should disable kexec in CI, and if we think kexec should be tested in CI, it should be a separate step after the first non-kexec boot.
The text was updated successfully, but these errors were encountered: