Repository navigation
ci: content checks only, on the smallest runner - #8
Merged
Merged
Conversation
The `smoke` job built the pinned harness on every PR (a from-source OpenBLAS build here, ten to sixteen minutes, twice per push) to prove something the recorder already proves before anything is published: `record_run.py` builds, verifies and times that exact revision on the host that owns the numbers. The harness is also built by the source repository's own CI for every PR there. What is left is content: the declarations, every recorded manifest, and the generated index, in one job on `ubuntu-slim`. It is the only required check on `main`, and auto-merge is enabled, so a recording or documentation PR merges by itself once the content is consistent.
shinaoka
enabled auto-merge
October 13, 2026 10:01
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
1 participant
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.
The measurement runs locally:
record_run.pybuilds, verifies and times the pinned checkout on the host that owns the numbers and publishes nothing unless all three succeed. Thesmokejob re-proved the harness builds on every PR at ten to sixteen minutes (twice per push), duplicating what the recorder and the source repository's own CI already gate. What is left for this repository is content: the declarations, every recorded manifest, and the generated index, in one job onubuntu-slim. It is the only required check onmain, and auto-merge is enabled, so a recording or documentation PR merges by itself once the content is consistent. Superseded runs on the same branch are cancelled.