Skip to content

[CI] Drop the duplicate gfx950 test runner and revert the nightly README badges - #1093

Closed
coderfeli wants to merge 2 commits into
mainfrom
ci/dedup-gfx950-runners
Closed

[CI] Drop the duplicate gfx950 test runner and revert the nightly README badges#1093
coderfeli wants to merge 2 commits into
mainfrom
ci/dedup-gfx950-runners

Conversation

@coderfeli

Copy link
Copy Markdown
Collaborator

Two small CI cleanups, both on top of main.

Drop the duplicate gfx950 runner

linux-flydsl-mi355-1 and linux-flydsl-mi35x-1 are the same target:

Runner runner-config.yml parse_bench.py arch
linux-flydsl-mi355-1 MI355, 1 GPU gfx950
linux-flydsl-mi35x-1 MI350, 1 GPU gfx950

Every push therefore ran the identical RUN_TESTS_FULL=1 scripts/run_tests.sh
twice on identical hardware — see run 33710068450,
where both were still going long after mi325 and navi had finished. The same
duplication existed for the -8 pair in the multi-gpu matrix.

This drops the mi35x entries from test, test-skip, multi-gpu
(flydsl.yaml) and the wheel test matrix (test-whl.yaml).

Why keep mi355 and not mi35x: the main branch ruleset requires
test (linux-flydsl-mi325-1) and test (linux-flydsl-mi355-1).
test (linux-flydsl-mi35x-1) is not required, so keeping mi355 means no
branch-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 shared
label 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.md hunk of #1091, restoring the badge row to
CI / Benchmark / Dashboard / Docs. The three nightly integration workflows
themselves are untouched and still run on schedule; this only removes the
links. The prepare-mlir manylinux changes from that commit are left fully
in place.

Verification

🤖 Generated with Claude Code

coderfeli and others added 2 commits September 3, 2026 06:12
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
coderfeli force-pushed the ci/dedup-gfx950-runners branch from 83e04a9 to 7e937bc Compare September 3, 2026 06:51
@coderfeli coderfeli closed this Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant