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 f9bee22
Browse filesBrowse the repository at this point in the historyBrowse files
docs: record the live ci-spot pool and hosted fallbacks
Supersede the stopgap sentences from 3484a7c, squash-merged as 693fd9e (pineforge-4pass#415, CR-170). Reword the runner-selection and timing assumptions from d093560 (pineforge-4pass#290) and the documentation-only runner sentence from 133f571 (pineforge-4pass#308); preserve the platform limits from 2394ba2 (pineforge-4pass#373).
Record the 2026-10-18 live-pool bulletin, exact fragment and environment labels, class allocation, actor allowlist, hosted matrix legs and event fallbacks. Keep historical timings separate from unmeasured pool performance. No local verification run under the executor no-run rule.
Each proof job waits for `changes` alone, a few seconds once the light ci-spot
830
+
class or its hosted fallback takes it, and skips only when `changes` succeeded
831
+
and answered documentation-only: `!cancelled() && (needs.changes.result != 'success' ||
832
832
needs.changes.outputs.docs_only != 'true')`. `preflight` waits for nothing.
833
833
The advisory `build` aggregate passes a proof job that succeeded, or one that
834
834
was skipped under that same answer. A proof job skipped for any other reason
@@ -887,41 +887,84 @@ does not assume a build optimization without evidence.
887
887
888
888
## Runners and time limits
889
889
890
-
Every job in `ci.yml`, `native-live.yml` and `corpus-parity.yml` uses the free
891
-
standard runners for every event, including pushes, schedules, manual
892
-
dispatches and pull requests from this repository or a fork. Linux jobs use
893
-
`ubuntu-24.04` (4 vCPU, 16 GB); the macOS `build` legs use `macos-26` (M1,
894
-
3 cores, 7 GB). Larger runners bill even for a public repository, and their
895
-
cost exceeded US$3,000: the owner's 2026-10-18 cost stop puts every job on
896
-
standard runners. This is a stopgap until the ci-spot pool is live; its labels
897
-
will replace the standard runner labels when that pool is ready.
890
+
The ci-spot pool is live as of 2026-10-18 (bulletin #613, L6, 22:34). Linux
891
+
x64 jobs use the fragments in `pf-ci-spot`'s `workflows/engine-x64-16.yml`
892
+
and `workflows/public.yml` at `pf-ci-spot` commit `1fe46216` (bulletins
893
+
#614/#615), with these exact label arrays:
894
+
895
+
| Jobs | Fragment and labels | Pool machine |
896
+
| --- | --- | --- |
897
+
| Linux `build` legs, `sanitizers`, `kernel-only`, all three `native-live` profiles, both corpus-parity jobs, release `prebuilt` Linux x64 leg |`engine-x64-16.yml`: `["self-hosted","pf-ci","pf-ci-x64-16"]`| e2-standard-16, 16 vCPU, 64 GB, 100 GB disk; engine only |
898
+
|`changes`, `preflight`, both aggregate jobs, docs `build`, release metadata and hub notification, manual baseline promotion |`public.yml`: `["self-hosted","pf-ci","pf-ci-x64"]`| e2-standard-4, 4 vCPU, 16 GB, 30 GB disk |
899
+
900
+
This replaces the temporary standard-runner stopgap recorded by `3484a7c40`
901
+
and squash-merged in `693fd9e68` (#415, CR-170) after GitHub larger-runner
902
+
costs exceeded US$3,000. The runner-selection and timing sentences being
903
+
reworded originated in `d0935605c` (#290), and the documentation-only runner
904
+
sentence in `133f57148` (#308). The platform job limits from `2394ba2fc`
905
+
(#373) remain in force.
906
+
907
+
Each Linux x64 job uses the fragment's expression verbatim and sets its
908
+
matching array as a job-level **string**`PF_CI_LABELS`, merged into any
909
+
existing job environment. The engine build fragment is:
0 commit comments