ci(gfx11): add weekly master+gfx11 builds on frozen ROCm 7.14#64
Open
jimw567 wants to merge 1 commit into
Open
ci(gfx11): add weekly master+gfx11 builds on frozen ROCm 7.14#64jimw567 wants to merge 1 commit into
jimw567 wants to merge 1 commit into
Conversation
jimw567
force-pushed
the
jimwu.gha-weekly-714-builds
branch
from
July 24, 2026 00:33
5bb53b6 to
e1b0278
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.
Summary
Extends the
Build gfx11 + ROCmworkflow from a single nightly build to three variants, driven by a newsetupmatrix job:gfx11gfx11-rocm-nightlymastermaster-rocm-714gfx11gfx11-rocm-714The two new 7.14 variants build weekly (Thursday, ahead of weekend regressions) so we can run regressions against a fixed ROCm 7.14 while the llama.cpp source varies week to week.
Details
setupjob emits the build matrix from the event: push/PR build only variant A's shape (triggering ref + latest, no release) so PR CI cost/latency is unchanged;workflow_dispatchpicks legs via abuild_setinput (nightly/weekly/all).X.Ychannel (e.g.7.14) -> highesttherock-dist-linux-multiarch-7.14.0a*tarball, alongsidelatest(highest overall) and an explicit pinned version override. The 7.14 line is frozen at7.14.0a20260624(last build before 7.15 alphas began), so "7.14 release" is deterministic.build-ubuntu/test-gfx/create-releaseare all matrixed over the variants. Per-variant ccache keys and artifact names avoid cross-variant thrash/collision; each build writesbuild-meta.txt(ref, commit, ROCm version) into its artifact so downstream jobs read provenance without fragile matrix outputs.create-releasedeletes and recreates each variant's tag at the exact built commit, so each tag always points at the newest build.Note: variant A's release tag changes from dated
b<YYYYMMDD>to the rollinggfx11-rocm-nightly.Cadence wiring
GitHub cron only fires from the default branch, so the weekly build uses the existing external-cron mechanism (same as the nightly). Add on the CI host:
Test plan
build_set=nightly(create_release=false) - confirm 1 leg (A), builds latest ROCm, gfx1151 test passes.build_set=weekly(create_release=false) - confirm 2 legs (B master, C gfx11), both resolve ROCm 7.14.0a20260624, gfx1151 tests pass.build_set=weekly create_release=true- confirm rolling tagsmaster-rocm-714andgfx11-rocm-714publish at the built commits.