ci: neutralize upstream self-hosted-runner jobs on the fork - #87
Closed
jimw567 wants to merge 1 commit into
Closed
Conversation
Upstream (ggml-org) runs many CI jobs on its own self-hosted runner fleet (labels: fast, X64, CPU, llama-server, PLAYWRIGHT, NVIDIA, etc.). The fork has no runners with those labels, so on PRs/pushes these jobs queue until GitHub's 24h max-runtime cap cancels them, showing as red checks. Two fixes, both fork-local (DO NOT UPSTREAM): - Slim/sanitize jobs that only need a generic runner -> runs-on: ubuntu-24.04 (check-vendor, pre-tokenizer-hashes, python-check-requirements, python-type-check, build-sanitize, server-sanitize, update-ops-docs), matching the existing editorconfig/code-style conversion. - Dedicated self-hosted workflows whose hardware the fork lacks -> gate each job with `if: github.repository == 'ggml-org/llama.cpp'` so it no-ops on the fork but merges cleanly from upstream (build-self-hosted, server-self-hosted, ui-self-hosted, build-openvino).
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.
Upstream (ggml-org) runs many CI jobs on its own self-hosted runner fleet (labels: fast, X64, CPU, llama-server, PLAYWRIGHT, NVIDIA, etc.). The fork has no runners with those labels, so on PRs/pushes these jobs queue until GitHub's 24h max-runtime cap cancels them, showing as red checks (e.g. the cancelled checks on PR #85).
Two fixes, both fork-local (each carries a DO NOT UPSTREAM comment):
if: github.repository == 'ggml-org/llama.cpp'so it no-ops on the fork but merges cleanly from upstream: build-self-hosted (12 jobs), server-self-hosted (2), ui-self-hosted (3), build-openvino (1).11 workflows changed. All YAML validated; verified no push/PR-triggered self-hosted job remains unguarded.