[CI] Drop the duplicate gfx950 test runner and revert the nightly README badges - #1093
Closed
coderfeli wants to merge 2 commits into
Closed
[CI] Drop the duplicate gfx950 test runner and revert the nightly README badges#1093coderfeli wants to merge 2 commits into
coderfeli wants to merge 2 commits into
Conversation
The three nightly integration badges added in #1091 crowd the badge row without adding much signal. Restore the README badge list to CI, Benchmark, Dashboard and Docs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
linux-flydsl-mi355-1 and linux-flydsl-mi35x-1 are both gfx950, so every push ran the same RUN_TESTS_FULL suite twice on identical hardware; the same holds for the -8 pair in the multi-gpu matrix. Keep the mi355 runners, which are the ones named by the required status checks on main. These are ARC scale sets rather than labelled self-hosted runners, so runs-on has to name one exactly and GitHub cannot race the two pools and give the job to whichever is free. Dropping one entry statically is the only option. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
coderfeli
force-pushed
the
ci/dedup-gfx950-runners
branch
from
September 3, 2026 06:51
83e04a9 to
7e937bc
Compare
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 small CI cleanups, both on top of
main.Drop the duplicate gfx950 runner
linux-flydsl-mi355-1andlinux-flydsl-mi35x-1are the same target:runner-config.ymlparse_bench.pyarchlinux-flydsl-mi355-1gfx950linux-flydsl-mi35x-1gfx950Every push therefore ran the identical
RUN_TESTS_FULL=1 scripts/run_tests.shtwice on identical hardware — see run 33710068450,
where both were still going long after mi325 and navi had finished. The same
duplication existed for the
-8pair in themulti-gpumatrix.This drops the
mi35xentries fromtest,test-skip,multi-gpu(
flydsl.yaml) and the wheeltestmatrix (test-whl.yaml).Why keep mi355 and not mi35x: the
mainbranch ruleset requirestest (linux-flydsl-mi325-1)andtest (linux-flydsl-mi355-1).test (linux-flydsl-mi35x-1)is not required, so keeping mi355 means nobranch-protection change is needed and there is no window where PRs stall
waiting on a check that is no longer reported.
Why not race the two pools: these are ARC scale sets, not labelled
self-hosted runners, so
runs-on:must name one exactly. There is no sharedlabel that would let GitHub hand the job to whichever pool is free, and both
matrix jobs dispatch simultaneously with no way to observe each other.
Statically dropping one entry is the only available option.
Revert the nightly README badges
Reverts only the
README.mdhunk of #1091, restoring the badge row toCI / Benchmark / Dashboard / Docs. The three nightly integration workflows
themselves are untouched and still run on schedule; this only removes the
links. The
prepare-mlirmanylinux changes from that commit are left fullyin place.
Verification
testandtest-skipmatrices remain identical (they must be, ordocs-only PRs hang on the required checks).
README.mdis byte-identical to its pre-[CI] accelerate prepare-mlir: run the CPU builder in the manylinux image #1091 state.manylinux/prepare_runnerlines.🤖 Generated with Claude Code