ci: run each suite for what can affect it; merges no longer repeat the pull request's run #332

Merged

dcharlot merged 2 commits from ci/lean-triggers into main 2026-10-19 06:02:04 -04:00

Conversation 0 Commits 2 Files changed 27 +75 -440

dcharlot commented 2026-10-19 02:49:15 -04:00

Owner

Copy link

The owner asked to remove CI bottlenecks. The Linux arm64 runner (3 jobs at a time) carried about 100 queued runs, most of them for suites that a pull request's diff could not affect, and every merge to main re-ran what its pull request had already run.

What changes

1. Merges no longer repeat the pull request's run. 27 workflows lose their push-to-main trigger and gain a nightly schedule, staggered between 04:00 and 08:59 UTC. A nightly run has no pull-request context, so every gate answers true and the full suite runs. That is the backstop for two pull requests that each passed but break together. repo-checks keeps its push trigger, because one of its steps runs only on a push. Workflows that already had a weekly schedule now run nightly. standards-build's comments are updated to match.

2. Shared files no longer fire heavy suites. wai-http, wai-jpegai-e2e, wai-neural-gates, wai-pack, wai-quantum-webgpu, wai-sota-vectors, wai-web-reach and wai-web-wasm drop wai/wai-rs/Cargo.toml, wai/wai-rs/src/lib.rs, wai/registry/** and wai/registry/capabilities.json from their paths. Every new feature or capability touches those files. wai/wai-rs/Cargo.lock stays, so a dependency change still runs them. wai-conformance keeps its registry trigger, because it checks the registry.

3. wai-http's falsify shards (about 1.5 hours of arm64 time) now gate on their own output, falsify. It is true when the pull request's diff touches one of these:

   • the files the patches in http-conformance/falsify/ modify: http_binding/**, container.rs, sig.rs, jwp_hash.rs, jwp_delivery.rs, hls_render.rs, wai_video_manifest.rs, and bin/wai_cli/http*;
   • the corpus and its verifier;
   • bin/wai_http_vectors.rs;
   • the workflow itself.

   It is also true nightly, and whenever the diff cannot be read, so it fails open. Other changes on wai-http's list still run its corpus jobs.

Trade-off

Before, a break that appears only when two separately green pull requests combine on main showed right after the merge. Now it shows in the next nightly run.

Checks

• every workflow file parses (Ruby's YAML loader);
• check-workflow-concurrency.sh, pr-touches-paths-selftest.sh, check-tests-in-ci.py and check-orphan-sources.py all pass;
• the falsify gate's pattern answers false for a live-rooms or registry change and true for sig.rs.

🤖 Generated with Claude Code

The owner asked to remove CI bottlenecks. The Linux arm64 runner (3 jobs at a time) carried about 100 queued runs, most of them for suites that a pull request's diff could not affect, and every merge to main re-ran what its pull request had already run. ## What changes 1. **Merges no longer repeat the pull request's run.** 27 workflows lose their push-to-main trigger and gain a nightly schedule, staggered between 04:00 and 08:59 UTC. A nightly run has no pull-request context, so every gate answers `true` and the full suite runs. That is the backstop for two pull requests that each passed but break together. `repo-checks` keeps its push trigger, because one of its steps runs only on a push. Workflows that already had a weekly schedule now run nightly. `standards-build`'s comments are updated to match. 2. **Shared files no longer fire heavy suites.** `wai-http`, `wai-jpegai-e2e`, `wai-neural-gates`, `wai-pack`, `wai-quantum-webgpu`, `wai-sota-vectors`, `wai-web-reach` and `wai-web-wasm` drop `wai/wai-rs/Cargo.toml`, `wai/wai-rs/src/lib.rs`, `wai/registry/**` and `wai/registry/capabilities.json` from their paths. Every new feature or capability touches those files. `wai/wai-rs/Cargo.lock` stays, so a dependency change still runs them. `wai-conformance` keeps its registry trigger, because it checks the registry. 3. **`wai-http`'s falsify shards** (about 1.5 hours of arm64 time) now gate on their own output, `falsify`. It is true when the pull request's diff touches one of these: - the files the patches in `http-conformance/falsify/` modify: `http_binding/**`, `container.rs`, `sig.rs`, `jwp_hash.rs`, `jwp_delivery.rs`, `hls_render.rs`, `wai_video_manifest.rs`, and `bin/wai_cli/http*`; - the corpus and its verifier; - `bin/wai_http_vectors.rs`; - the workflow itself. It is also true nightly, and whenever the diff cannot be read, so it fails open. Other changes on `wai-http`'s list still run its corpus jobs. ## Trade-off Before, a break that appears only when two separately green pull requests combine on main showed right after the merge. Now it shows in the next nightly run. ## Checks - every workflow file parses (Ruby's YAML loader); - `check-workflow-concurrency.sh`, `pr-touches-paths-selftest.sh`, `check-tests-in-ci.py` and `check-orphan-sources.py` all pass; - the falsify gate's pattern answers `false` for a live-rooms or registry change and `true` for `sig.rs`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-10-19 02:49:16 -04:00

ci: run each suite for what can affect it; re-runs after a merge become nightly ... ac511a78ff

- 27 workflows that ran on pull requests and again on every push to main now run on
  pull requests and nightly (staggered 04:00-08:59 UTC). A merge no longer repeats what
  its pull request ran; the nightly run is the backstop for a combination of two
  pull requests that each passed. repo-checks keeps its push trigger: one of its
  steps runs only on a push.
- Eight heavy WAI workflows (http, jpegai-e2e, neural-gates, pack, quantum-webgpu,
  sota-vectors, web-reach, web-wasm) no longer fire on wai-rs/Cargo.toml,
  wai-rs/src/lib.rs or the registry, which every new feature and capability touches.
  Cargo.lock stays a trigger, so a dependency change still runs them; wai-conformance
  keeps the registry, which it checks.
- wai-http's falsify shards (about an hour and a half of runner time) run when a pull
  request changes the code the falsify patches break, the HTTP corpus, its verifier or
  the workflow, and nightly; other changes on wai-http's list run its corpus jobs only.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot added 1 commit 2026-10-19 06:01:42 -04:00

Merge origin/main into ci/lean-triggers; wai-conformance keeps no push block ... ea0a855dcb

Main's new path entries in the push block (the live extensions) are also in the pull-
request list, which stays; the push block goes, as this branch intends.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot merged commit 046575eaf9 into main 2026-10-19 06:02:04 -04:00

dcharlot referenced this pull request from a commit 2026-10-19 06:02:05 -04:00

Merge pull request 'ci: run each suite for what can affect it; merges no longer repeat the pull request's run' (#332) from ci/lean-triggers into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!332

No description provided.