You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8154993
Browse filesBrowse the repository at this point in the historyBrowse files
authored
ci: move post-merge verification to GCP and forbid paid runners (#555)
Route the amd64 post shards (Release, Debug, kernel, sanitizers), the native
shards and both live sanitizer profiles to ["self-hosted","pf-gcp-post"].
Shard counts, matrices, verification commands, aggregates and check names are
unchanged. The workflow checker now refuses every numeric pf-linux-x64 and
pf-linux-arm64 label and every large/larger/xlarge suffix at every job, with no
per-job exception, and the paid label declarations leave the actionlint config.
docs/ci.md is rewritten line for line and stays at 2014 lines. These sentences,
introduced by 3ea5a0d (the routing and capacity claims), are replaced:
- "Post Release/Debug/kernel and native shards use `pf-linux-x64-16`; post
sanitizers use `pf-linux-x64-32`; native-live sanitizers use
`pf-linux-x64-64`."
- "One full post run needs four x64-16 and two x64-64 native runners
concurrently."
- "The amd64 post build shards request hosted `pf-linux-x64-16`; the two arm64
post cells run on hosted `ubuntu-24.04-arm`."
- "Hosted exceptions include the named light jobs, amd64 post shards, native
profiles, arm64 and the existing release/promotion pins."
- "`native-live.yml` runs four `native` shards on hosted `pf-linux-x64-16`;
`live-sanitizers` and `live-tsan` each build once on hosted
`pf-linux-x64-64`."
- "The four amd64 post legs and native verification use hosted runners; their
aggregates use the light image."
- The `ci-post.yml` and `native-live.yml` rows of the workflow table that name
the pf-linux labels.
- "Hosted shards also run on a branch dispatch; the remaining post fleet still
requires `main`."
- "Release uses four `build` shards, Debug two `build-debug` shards, and kernel
two shards on 16 cores; sanitizers uses four on 32 cores."
- "`HOSTED_JOB_RUNNERS` pins hosted jobs; its larger/arm64 exceptions exclude
PR callers."
- "Larger labels are allowed only at their exact named jobs' `runs-on` keys;
`larger_runner` keys stay refused."
The historical timing sentence introduced by 0212cab keeps every measured
value and only names the former paid pool. The rollback sentence introduced by
b0f4341 no longer tells a reader to restore a paid label.
Co-authored-by: ci-cx <ci-cx@invalid>
Co-authored-by: Claude Sonnet 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: docs/ci.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,11 +69,11 @@ successful runs on `main` save that cache namespace.
69
69
70
70
Verification jobs keep literal runner pins at the workflow boundary: PR build/preflight and parity subset use `["self-hosted","pf-gcp-pr"]`;
71
71
post preflight/parity and credentialed docs use `["self-hosted","pf-gcp-post"]`.
72
-
Post Release/Debug/kernel and native shards use `pf-linux-x64-16`; post sanitizers
73
-
use `pf-linux-x64-32`; native-live sanitizers use `pf-linux-x64-64`. No job routes by event.
72
+
Post Release/Debug/kernel and native shards, post sanitizers and both native-live sanitizer
73
+
profiles use `["self-hosted","pf-gcp-post"]`. No job routes by event.
74
74
Hosted `ubuntu-24.04` runs all eight `authz` jobs, both CI `changes`/`build-gate` jobs, all post/native aggregates and `docs.yml`'s `build`.
75
75
These light, secret-free jobs need no VM-only tools, mounts or caches.
76
-
Local reusable calls still cannot mix PR and post-merge verification fleets. One full post run needs four x64-16 and two x64-64 native runners concurrently.
76
+
Local reusable calls still cannot mix PR and post-merge verification fleets. A full post run schedules 22 post-fleet jobs; the parity calls share one concurrency group.
77
77
78
78
The manual `release-ruleset-probe.yml` workflow runs `authz` on
79
79
hosted `ubuntu-24.04` and `probe` on `["self-hosted","pf-gcp-post"]`.
@@ -183,9 +183,9 @@ source-only header trees, and compile the native public roots and examples;
183
183
the preflight source guard rejects those includes before a build.
184
184
185
185
CI uses Ubuntu 24.04 amd64 and arm64 cells and selects Python 3.12 explicitly.
186
-
The amd64 post build shards request hosted `pf-linux-x64-16`; the two arm64 post cells run on
186
+
The amd64 post build shards use the post-merge GCP fleet; the two arm64 post cells run on
187
187
hosted `ubuntu-24.04-arm`. All three build jobs refuse an OS mismatch.
188
-
Hosted exceptions include the named light jobs, amd64 post shards, native profiles, arm64 and the existing release/promotion pins.
188
+
Hosted exceptions include the named light jobs, arm64 and the existing release/promotion pins.
189
189
CMake uses the same interpreter as the
190
190
verification driver, so its Python checks do not switch to a different system
191
191
Python. CTest must discover tests; an empty suite is a failure. Which runner
@@ -617,8 +617,8 @@ requires the WebSocket test.
617
617
The runner's curl version floor still applies at configure time.
618
618
`live-tsan` runs the same inventory in a separate ThreadSanitizer build,
619
619
checks every runner compile unit for instrumentation, and stops on a race.
620
-
`native-live.yml` runs four `native` shards on hosted `pf-linux-x64-16`;
621
-
`live-sanitizers` and `live-tsan` each build once on hosted `pf-linux-x64-64`.
620
+
`native-live.yml` runs four `native` shards on the post-merge GCP fleet;
621
+
`live-sanitizers` and `live-tsan` each build once on that same fleet.
622
622
Both matrices keep `fail-fast: false`, pinned WebSocket curl and profile caches. A failed cell does not cancel its peers.
623
623
Native compiler keys and diagnostic artifacts also carry the shard index.
624
624
The `native-live (native)` aggregate requires all four successful summary proofs;
@@ -1482,7 +1482,7 @@ maintainers' full verification where it runs the row; the pull request does not
1482
1482
see it. That delay is not zero. In the one hosted push run sampled
1483
1483
(`39126947405`) the Release job took 1876 s, `kernel-only` 3022 s, Debug 3416
1484
1484
s, `sanitizers` 2707 s and the native cell 3132 s; the older
1485
-
`pf-linux-x64-16` runners' medians over five runs were 1815, 1812, 1770, 2050
1485
+
paid 16-core runners' medians over five runs were 1815, 1812, 1770, 2050
1486
1486
and 1838 s, and a push run on the current pool has not been measured. The
1487
1487
pull-request wall time under D1 is to be measured on real PR runs, typical and
1488
1488
tail; it is not claimed as met against the owner's 15-minute target.
@@ -1648,17 +1648,17 @@ runs, and this page does not claim either target as met.
1648
1648
## Runners and time limits
1649
1649
1650
1650
Credentialed work and the remaining full profiles retain their VM pins.
1651
-
The four amd64 post legs and native verification use hosted runners; their aggregates use the light image.
1651
+
The four amd64 post legs and native verification use the post-merge GCP fleet; their aggregates use the light image.
1652
1652
The native matrix is exactly `1..4` with `--ctest-shard I/4`; live sanitizers are unsharded. Each runner label remains a literal, checked per job:
|`corpus-parity-subset.yml`| Reusable call from PR CI |`authz`: hosted `ubuntu-24.04`; subset: `["self-hosted","pf-gcp-pr"]`|
1658
1658
|`docs.yml`|`pull_request`, except `.github/**`-only diffs |`authz` and `build`: hosted `ubuntu-24.04`|
1659
-
|`ci-post.yml`| Push to `main`, 01:30 UTC schedule, dispatch | Light jobs and four leg aggregates: `ubuntu-24.04`; Release/Debug/kernel shards: `pf-linux-x64-16`; sanitizers shards: `pf-linux-x64-32`; `build-arm`: `ubuntu-24.04-arm`; preflight tiers: `["self-hosted","pf-gcp-post"]`|
1659
+
|`ci-post.yml`| Push to `main`, 01:30 UTC schedule, dispatch | Light jobs and four leg aggregates: `ubuntu-24.04`; Release/Debug/kernel and sanitizer shards plus preflight tiers: `["self-hosted","pf-gcp-post"]`; `build-arm`: `ubuntu-24.04-arm`|
1660
1660
|`corpus-parity.yml`| Schedule, dispatch, post CI callers |`authz`: hosted `ubuntu-24.04`; both parity jobs: `["self-hosted","pf-gcp-post"]`|
1661
-
|`native-live.yml`| Dispatch and post CI callers, including branch dispatch |`authz` and both aggregates: hosted `ubuntu-24.04`; four native shards: `pf-linux-x64-16`; `live-sanitizers` and `live-tsan`: `pf-linux-x64-64`|
1661
+
|`native-live.yml`| Dispatch and post CI callers on `main`|`authz` and both aggregates: hosted `ubuntu-24.04`; four native shards, `live-sanitizers` and `live-tsan`: `["self-hosted","pf-gcp-post"]`|
The post fleet admits only push, schedule and dispatch on engine `main` and
@@ -1667,18 +1667,18 @@ refuses all PR events. Reusable workflows inherit their caller's event.
1667
1667
follow local calls to a fixed point, refuse mixed event classes and require
1668
1668
literal VM arrays outside the exact hosted pins; job conditions cannot excuse routing.
1669
1669
Fork PRs on hosted runners run without our secrets, so the VM-only fork-refusal hook is not needed.
1670
-
Hosted shards also run on a branch dispatch; the remaining post fleet still requires `main`.
1671
-
Rollback: relabel the affected job to its prior `pf-gcp-pr` or `pf-gcp-post` array and restore its checker/test pin.
1670
+
Post-fleet shards require `main` for dispatch; hosted arm64 keeps its fixed pin.
1671
+
Rollback may restore an earlier GCP fleet pin; paid larger-runner labels remain refused.
1672
1672
1673
1673
The four full build checks are `build (ubuntu-24.04, Release)`,
1674
1674
`build (ubuntu-24.04, Debug)`, `build (ubuntu-24.04-arm, Release)` and
1675
1675
`build (ubuntu-24.04-arm, Debug)`. Release uses four `build` shards, Debug two
1676
-
`build-debug` shards, and kernel two shards on 16 cores; sanitizers uses fouron 32 cores.
1676
+
`build-debug` shards, and kernel two shards; sanitizers uses four, all on the post-merge GCP fleet.
1677
1677
Every shard builds the full tree and runs `--ctest-shard I/N` at the runner's core count. Each build refuses an OS mismatch before checkout.
1678
1678
Each leg aggregate retains its old check name and requires its own matrix's success. The two arm64 cells share `build-arm` on hosted `ubuntu-24.04-arm`. All three build jobs use the same verification steps and profiles.
1679
1679
Shard jobs and leg aggregates skip together only on classified docs-only changes.
1680
1680
One cache key per architecture/profile/SHA is restored by all shards; only shard 1 saves it.
1681
-
`HOSTED_JOB_RUNNERS` pins hosted jobs; its larger/arm64 exceptions exclude PR callers. The PR build remains
1681
+
`HOSTED_JOB_RUNNERS` pins hosted jobs and post-fleet verification arrays; arm64 exceptions exclude PR callers. The PR build remains
1682
1682
`build (ubuntu-24.04, Release)` and its aggregate remains `build`.
1683
1683
1684
1684
Release and promotion use the isolated release fleet:
@@ -1729,7 +1729,7 @@ merge time, and supply readable identity fields; failures there refuse red.
1729
1729
Legacy `PF_CI_LABELS` metadata does not select runners. Verification and
1730
1730
parity commands use `$(getconf _NPROCESSORS_ONLN)` for parallelism.
1731
1731
No job or step declares `timeout-minutes`, and no proof continues on error.
1732
-
Larger labels are allowed only at their exact named jobs' `runs-on` keys;
1732
+
Every paid larger-runner label is refused in every workflow, including pinned jobs;
1733
1733
`larger_runner` keys stay refused. GitHub's platform maximum remains the only time bound.
1734
1734
1735
1735
The read-only `promote-guard` stays hosted on `ubuntu-latest`; the credential
0 commit comments