Repository navigation
docs: record that v0.3.2 was verified, not just diagnosed - #8
Merged
Merged
Conversation
The v0.3.2 entry explained the regression and the fix and then stopped at the two numbers that proved the problem. Anyone reading it later could not tell whether the fix worked. It now carries all three measurements, the per-check breakdown behind them, and the one row that looks wrong and is not: the `main` lane comes out 38s slower than it was sequentially, because two lanes jointly ask for all four vCPUs where the sequential job asked for two. That is the trade working -- `main` was never the critical path. Also records why a self-hosted figure is quoted from inside a single run: absolute step times there swing 40s between runs of the same commit, because the layer cache and the hook-cache volume survive. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R7Y1jesjfgxHeqtKJCvay6
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.
The v0.3.2 changelog entry explained the regression and the fix, then stopped at the two numbers that proved the problem. A reader could not tell whether the fix actually worked.
It now carries all three measurements from trentina's
sdlc cistep on a GitHub-hosted 4-vCPU runner — fresh VMs with no layer cache, so they are directly comparable:Plus the per-check breakdown, and the one row that looks like a defect and is not: the
mainlane is 38s slower than it was sequentially, because the two lanes jointly ask for all four vCPUs where the sequential job asked for two. That is the trade working as designed —mainwas never the critical path, so trading 38s there for 223s overall is the point.Also records why a self-hosted number is quoted from inside a single run rather than as a before/after: on a runner that keeps its layer cache and the hook-cache volume, absolute step times swung 40s across three runs of the same commit (83s, 123s, 127s), driven by startup 22s→2s and pytest 82s→62s. The within-run lane saving was stable at 64s / 68s / 68s.
Docs only — no version bump, so this does not cut a release.
🤖 Generated with Claude Code
https://claude.ai/code/session_01R7Y1jesjfgxHeqtKJCvay6