ci: unbreak fork CI — dead self-hosted labels + invalid sycl workflow#105
Merged
Conversation
Three fork-side CI defects, all inherited from upstream's runner topology: - build-cmake-pkg.yml: [self-hosted, Linux, CPU] matches no runner in this org (only ht-org-k8s-* with Linux,X64,k8s exists) -> the job queued forever and the 'CI (cpu)' workflow has never concluded since the 2026-06-07 CI refactor sync. GitHub-hosted ubuntu-latest (repo is public). - python-lint.yml: [self-hosted, fast] same story; flake8 dead-queued on every push since 2026-05-24. ubuntu-latest. - build-sycl.yml: #74 stripped the auto-triggers, but the file itself is schema-INVALID (all jobs commented out = empty jobs map), and GitHub creates a zero-job 'failure' run on every push for invalid workflows regardless of triggers. Add a never-running placeholder job so the file parses; drop it when upstream re-enables SYCL CI.
…p unused np binding
The linter has been dead-queued since 2026-05-24 (runner label); reviving
it surfaced 36 violations, all in downstream diagnostic scripts:
- scripts/{gguf-meta,compare-dflash-weights,dflash-logit-parity}.py write
their reports to stdout by design — NP100 (no print(), use logging)
targets library code. Per-file-ignores in .flake8.
- dflash-logit-parity.py: F841 — numpy presence-check kept, dead binding
dropped.
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.
Three fork-side CI defects, all inherited from upstream's runner topology. Together with #104 (TurboQ OOB) this makes the repo's CI actually able to go green.
1.
build-cmake-pkgqueued forever → CI (cpu) never concludesruns-on: [self-hosted, Linux, CPU]targets ggml-org's runner fleet. The only runner registered in this org isht-org-k8s-*(self-hosted, Linux, X64, k8s) — noCPUlabel, so the job has queued forever on every run since the 2026-06-07 CI refactor sync, leaving theCI (cpu)workflow permanently unconcluded (even on master, where every other leg passes). It's a plain cmake build+consume test →ubuntu-latest(repo is public, GitHub-hosted is free).2. flake8 Lint dead since 2026-05-24
runs-on: [self-hosted, fast]— same story, no such runner. Every run queues until GitHub expires it. →ubuntu-latest.3. build-sycl: zero-job "failure" run on every push
#74 stripped the auto-triggers, but the file is schema-invalid (all jobs commented out = empty
jobs:map), and GitHub surfaces invalid workflow files as a zero-job failure run on every push regardless of triggers — confirmed: pushes of refs containing #74's strip still produced failure runs. Fix: a never-running (if: false) placeholder job so the file parses. Delete when upstream re-enables SYCL CI.Validation