You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have tests that do upgrades, but they start from the *new* bootc.
Add a `just`+CI workflow that starts from a stable shipped image
(we just need to inject tmt deps + nu).
The readonly test then gains a helper which optionally performs
an upgrade to the new target.
IOW the flow is
- deploy stock image with unmodified bootc etc
- upgrade
- run readonly tests
It could of course make sense to run *all* of the tests this
way as an optional thing, nothing blocks that, but it would
be *another* entry in our matrix and we're going to need
to figure out how to wrangle that matrix size.
Also do to that we'd need to abstract over TMT_REBOOT_COUNT.
Assisted-by: OpenCode (Claude claude-opus-4-6)
Signed-off-by: Colin Walters <walters@verbum.org>
0 commit comments