ci: one heavy test suite per runner VM#2044
Open
cpunion wants to merge 2 commits into
Open
Conversation
Since the stage-5 backbone merged, the covered test run stacks four
heavy, llgo-building test packages (cl, ssa, internal/cabi, test/go)
on one runner; with the shared go-build cache their compile phases
fully overlap and the concurrent clang/lld burst has been killing
16GB ubuntu runners mid-run ('runner received a shutdown signal',
reproduced across main and every stage-5 branch) and starving mac
runners into go-list WaitDelay expirations (printval/returnorder/
abitype flakes).
Split the test job by suite (cl / ssa+cabi / test tree / rest): each
VM runs one heavy package, so the peak cannot stack by construction,
and wall time drops to the slowest single suite. Coverage still
uploads from every job; codecov merges per commit. The embedded
emulator step rides with cl, the std-symbol check with rest.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Structural fix for the post-backbone runner deaths (ubuntu exit-143 "shutdown signal" ~8 minutes into the heavy-package phase, reproduced on main and every stage-5 branch) and the mac go-list
WaitDelayflakes: the covered run stacks four heavy llgo-building test packages (cl, ssa, internal/cabi, test/go) on one VM, and warm shared caches let their compile phases fully overlap.Design (asymmetric, mindful of scarce mac runners)
cl/ssa+cabi/test tree/rest. Peak cannot stack by construction.cl+cabiandssa+testgo+rest. That restores the pre-backbone peak scale, which mac handled, at the cost of only +1 mac job.Rejected alternatives: raising budgets (hides it),
go test -p 2(lowers probability only).Wall time drops to the slowest group; coverage uploads from every job and codecov merges per commit. The embedded-emulator step rides with the cl suites, the std-symbol check with the rest suites.
Branch protection note: required check names change from
test (os, 19)totest (os, 19, <suite>).🤖 Generated with Claude Code