Repository navigation
ci(build): queue main runs instead of cancelling them; upload installer logs - #292
Merged
jeefy merged 1 commit intoSep 29, 2026
Merged
Conversation
…er logs A push to main cancelled the in-progress run for the previous merge (projectbluefin#289 cancelled 6d49f9b's run), so that version never released. Only pull requests now cancel superseded runs; main runs queue in the same group. The boot-test log upload also missed dist/dogfood-installer/, so the offline installer test's serial logs were lost on failure. Assisted-by: Claude Opus 5.5 via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Collaborator
Author
|
Correction to the description: GitHub keeps at most one running and one pending run per concurrency group, and a newer pending run always replaces the older pending one, regardless of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two CI fixes found while merging the punch-list follow-ups.
concurrency.cancel-in-progress: trueapplies topushto main too, so merging docs: follow-ups deferred from #276 #289 cancelled the build/release run for 6d49f9b and that version never shipped.cancel-in-progressis now${{ github.event_name == 'pull_request' }}: PRs still cancel superseded runs, while main runs queue in the same group and each one releases.Upload boot logscollecteddist/*/dogfood-*.loganddist/dogfood-install/*.logbut notdist/dogfood-installer/, where the ci: boot-test the offline USB installer end to end #277 offline installer test writes its serial and QEMU logs. ci(track-binaries): refresh amd64 and arm64 pins together, with tests #288 hit a1-enroll: no result within 600sfailure there with no logs to inspect. The same test passes locally on current main (cc139eb), so it looks like a runner flake, but the next occurrence should be debuggable.Tests: two new assertions in
tests/unit/test_release_workflow.py. Both fail if the change is reverted. pytest (569 passed, also in a clean tree withoutfiles/boot-keys), bats 74/74, docs-checks and actionlint all pass.