ci(sycl): drop auto-triggers (workflow has zero jobs upstream)#74
Merged
Conversation
All SYCL jobs in this workflow are commented out upstream (PR ggml-org#23705) to save Actions resources. With the upstream auto-triggers (push to master, pull_request matching ggml/src/ggml-sycl/**) still firing, every fork-sync that touches master creates a zero-job 'failure' run, polluting our Actions dashboard. Strip the auto-triggers on ht; keep workflow_dispatch so the job stays manually invokable if/when upstream re-enables SYCL CI. Will need to be re-applied after future master syncs that pull in the upstream version of this file.
This was referenced Jun 5, 2026
marksverdhei
added a commit
that referenced
this pull request
Jun 12, 2026
Same pattern as PR #74 (build-sycl.yml): upstream PR ggml-org#23705 commented out every job in this workflow, but the push:master + pull_request auto-triggers stayed live. Any PR touching ggml/src/ggml-cann/** would create a zero-job "failure" run. Keep workflow_dispatch so the workflow stays available for manual runs once jobs are re-enabled (which requires provisioning dedicated runners per the upstream TODO). Co-authored-by: marksverdhei <mark.sverdhei@gmail.com>
This was referenced Jun 12, 2026
marksverdhei
added a commit
that referenced
this pull request
Jun 12, 2026
…#105) * ci: unbreak fork CI — dead self-hosted labels + invalid sycl workflow 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. * ci(lint): flake8 green — NP100 per-file-ignores for stdout CLIs + drop 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. --------- Co-authored-by: marksverdhei <mark.sverdhei@gmail.com>
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.
Epoch #73 task 1: CI health.
What
All SYCL jobs in
.github/workflows/build-sycl.ymlare commented out upstream (ggml-org/llama.cpp#23705) to save GitHub Actions resources. With the upstream auto-triggers (push to master, pull_request matching ggml/src/ggml-sycl/**) still firing, every fork-sync that touches master creates a zero-job "failure" run and pollutes our Actions dashboard.Diff
Strip
push+pull_requestblocks fromon:; keepworkflow_dispatchso the job stays manually invokable.Maintenance note
Master sync (ggml-org#119 was the last one) brings in the upstream version of this file, which re-introduces the auto-triggers. The note in the file body explains what to re-apply after a sync. Filing as a recurring 'fix after master sync' item; may want a CI-side check that flags zero-job workflow runs eventually.
Verified
python3 -c 'import yaml; yaml.safe_load(open(".github/workflows/build-sycl.yml"))'— YAML parsesworkflow_dispatch:-only workflows are valid in GitHub Actions (nojobs:block required when there are no auto-triggers; though we still keep the commented-out block intact for the manual dispatch path to invoke when re-enabled)