ci: gate self-hosted-only workflows behind workflow_dispatch#19
Merged
Conversation
The elizaOS org has zero self-hosted runners registered (`gh api repos/elizaOS/llama.cpp/actions/runners` → total_count: 0), so any job pinned to self-hosted labels stays queued forever and fails to deliver a CI signal. Two workflows still relied on self-hosted runners on every push/PR: - `CI (self-hosted)` (build-self-hosted.yml) — 10 jobs across [self-hosted, Linux, NVIDIA / COOPMAT2], [self-hosted, macOS, ARM64], [self-hosted, Linux, Intel], [self-hosted, Windows, X64, Intel], [self-hosted, Linux, Intel, OpenVINO]. Restrict the whole workflow to `workflow_dispatch` only. Re-enable push/PR once a fleet exists. - `CI (openvino)` (build-openvino.yml) — the GPU matrix variant targets [self-hosted, Linux, Intel, OpenVINO]. Gate that variant behind a new `force_self_hosted` workflow_dispatch input; the CPU variant on ubuntu-24.04 still runs on every push/PR. Same approach as PR #18 used for cuda-runtime-validation.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
The elizaOS org has zero self-hosted runners (
gh api repos/elizaOS/llama.cpp/actions/runners→total_count: 0), so any job pinned to a self-hosted label stays queued indefinitely and never delivers a CI signal. Two workflows still relied on self-hosted runners on every push/PR; restrict them to manual trigger:CI (self-hosted)(.github/workflows/build-self-hosted.yml) — 10 jobs across[self-hosted, Linux, NVIDIA / COOPMAT2],[self-hosted, macOS, ARM64],[self-hosted, Linux, Intel],[self-hosted, Windows, X64, Intel],[self-hosted, Linux, Intel, OpenVINO]. Restrict the whole workflow toworkflow_dispatchonly.CI (openvino)(.github/workflows/build-openvino.yml) — the GPU matrix variant targets[self-hosted, Linux, Intel, OpenVINO]. Gate that variant on a newforce_self_hostedworkflow_dispatch input; the CPU variant onubuntu-24.04continues to run on every push/PR.Same approach as PR #18 used for
cuda-runtime-validation.Test plan
CI (self-hosted)runs auto-trigger on push to mainCI (openvino)runs only the CPU variant on push (ubuntu-24-openvino-CPU)gh workflow run "CI (self-hosted)"succeeds (or surfaces missing-runner state)