diff --git a/quest/m0/ci/README.md b/quest/m0/ci/README.md index 4bbc8732e17..1f1a9e79fd1 100644 --- a/quest/m0/ci/README.md +++ b/quest/m0/ci/README.md @@ -179,7 +179,6 @@ The historical samples locate candidates; they are not controlled benchmarks. - [Read-only pull-request CI](/quest/m0/ci/read-only-secrets.md) - write secrets and publisher identities reach only protected branches and tags, never a pushed branch - [Archive the @moq packages on JSR](/quest/m0/ci/jsr-retire.md) - once `release` stops publishing there, the maintainer archives every JSR package, ending its OIDC link - [Verify the R2 Rust cache](/quest/m0/ci/mbx-r2-verify.md) - confirm the hosted Nightly jobs reuse the previous Nightly, then measure restore time and expiry -- [Verify the Nix runtime cache](/quest/m0/ci/nix-cache-verify.md) - hosted Cache uploads `main`'s relay and CLI, and Smoke's nix channel substitutes them - [The Nix CI cache never expires a path the newest cached commit needs](/quest/m0/ci/nix-cache-expiry.md) - reused store paths outlive the bucket's 30-day expiry while a recent commit needs them - [Release tags push to nix.moq.dev, and Cachix stops taking writes](/quest/m0/ci/cachix-retire.md) - backport `release-nix.yml` and its Just module to `release`, drop `cachix.yml`, prove a tag substitutes from nix.moq.dev, then revoke the Cachix token (the cache stays for old tags) - [Measure the Linux cache effect of native media exclusions](/quest/m0/ci/hakari-followups.md) - scheduled Linux jobs measure cache reuse after unrelated tests stop compiling PipeWire and libclang diff --git a/quest/m0/ci/cachix-retire.md b/quest/m0/ci/cachix-retire.md index 323dfec3da5..1ea310ab30a 100644 --- a/quest/m0/ci/cachix-retire.md +++ b/quest/m0/ci/cachix-retire.md @@ -64,7 +64,3 @@ Public API: none. Wire: none. source builds once paths expired (`building '/nix/store/...uniffi-bindgen` in a job log), and refresh on a schedule or switch to a closure-aware collector (niks3) if they recur. - -## Related - -- [Verify the Nix runtime cache](/quest/m0/ci/nix-cache-verify.md) - the same cache's `main` evidence diff --git a/quest/m0/ci/mbx-r2-verify.md b/quest/m0/ci/mbx-r2-verify.md index 2daae41c551..59bfeb83a73 100644 --- a/quest/m0/ci/mbx-r2-verify.md +++ b/quest/m0/ci/mbx-r2-verify.md @@ -154,7 +154,3 @@ feature unification, so changed compiler inputs remain a separate cause. change, and count the Nightly jobs that rebuilt a crate the 14-day expiry deleted, listing as unknown any it cannot attribute. Bring the lifecycle back to the maintainer only if that count argues for lengthening it. - -## Related - -- [Verify the Nix runtime cache](/quest/m0/ci/nix-cache-verify.md) - the same R2 and Environment bootstrap for Nix diff --git a/quest/m0/ci/nix-cache-expiry.md b/quest/m0/ci/nix-cache-expiry.md index 7ede9dfda95..0910424f609 100644 --- a/quest/m0/ci/nix-cache-expiry.md +++ b/quest/m0/ci/nix-cache-expiry.md @@ -16,7 +16,3 @@ newer commits still need it. Then fix it so the guarantee also holds when no upload runs for 30 days: refreshing reused paths on upload alone does not cover such a gap. For example, a scheduled job refreshes the newest cached commit's closure, or the expiry deletes only paths no recent commit references. - -## Related - -- [Verify the Nix runtime cache](/quest/m0/ci/nix-cache-verify.md) - the scheduled Smoke check this protects diff --git a/quest/m0/ci/nix-cache-verify.md b/quest/m0/ci/nix-cache-verify.md deleted file mode 100644 index 34fe293d2d9..00000000000 --- a/quest/m0/ci/nix-cache-verify.md +++ /dev/null @@ -1,78 +0,0 @@ -# [XS] Verify the Nix runtime cache - -## Goal - -Hosted CI proves `main`'s `moq-relay` and `moq` runtime closures reach -`nix.moq.dev`: a successful Cache run uploads both, and a later Smoke nix run -substitutes them instead of compiling. - -## Plan - -[#5693](https://github.com/moq-dev/moq/pull/5693) wired `nix.moq.dev` into -CI. The maintainer ran the bootstrap in `infra/README.md` on 2026-10-19 and -2026-10-20. Check it with `curl https://nix.moq.dev/nix-cache-info`. - -[#6588](https://github.com/moq-dev/moq/pull/6588) restored `cache.yml`: -every merge to `main` pushes the dev shell's build closure for x86 Linux, ARM -Linux, and ARM macOS to `nix-ci-moq-dev` (`sh/gh/cache.sh`). Hosted CI -entering the dev shell is verified: Nightly run 40506938673 (2026-10-27) -substituted it in about a minute with nothing compiled, against 12-14 -minutes of source builds in the 2026-10-16 baseline. - -[moq-dev/moq#7662](https://github.com/moq-dev/moq/pull/7662) adds a Cache -`runtime` job (`sh/gh/cache-runtime.sh`) that pushes the `moq-relay` and `moq` -runtime closures, after their Crane dependency artifacts, on x86 Linux, -Smoke's only current nix platform (runtime caching decided 2026-10-29). -[moq-dev/moq#7431](https://github.com/moq-dev/moq/pull/7431) dropped Cachix -from `main` (decided 2026-11-02), so Smoke reads `nix.moq.dev` without write -credentials. - -Decided 2026-11-05 (maintainer, /quest-audit, -[moq-dev/moq#7975](https://github.com/moq-dev/moq/pull/7975)): ✅ keep only -this `main` evidence in m0 and move the release-tag proof, Cachix retirement, -and bucket sizes to an m2 quest behind the release cut. Not chosen: moving the -whole quest to m2; merging `main` into `release` now. - -Superseded the same day (maintainer, /quest-unblock): the release-tag proof, -Cachix retirement, and bucket sizes moved to -[Release tags push to nix.moq.dev](/quest/m0/ci/cachix-retire.md), which -backports `release-nix.yml` to `release` now instead of waiting for the cut. - -Recorded 2026-11-06 (/quest-unblock): #7662 merged 2026-11-05 22:15Z, and the -first successful Cache run after it, -[42119995773](https://github.com/moq-dev/moq/actions/runs/42119995773/job/127569533619), -uploaded both the `moq-cli` and `moq-relay` closures from its -`Runtime (ubuntu-24.04)` job. - -Use the scheduled and push runs; never dispatch Nightly for this evidence. - -Checked 2026-11-06 (/quest-unblock): the next scheduled Smoke, -[42245927828](https://github.com/moq-dev/moq/actions/runs/42245927828) -(2026-11-06, started 15:45Z), fetched the deps from `nix.moq.dev` but still -compiled both binaries. Smoke builds `github:moq-dev/moq#...` unpinned, so it -built main as of 16:28Z (2916531c19), whose Cache run was cancelled, rather -than its own head. Any Smoke that starts while main is ahead of its last -completed Runtime upload misses the same way. - -Confirmed 2026-11-06 (/quest-start, [moq-dev/moq#8114](https://github.com/moq-dev/moq/pull/8114)): -the miss was a commit mismatch, not a cache bug. The relay resolved -2916531c19 (Cache [42251988901](https://github.com/moq-dev/moq/actions/runs/42251988901) -cancelled) and the CLI, built five minutes later, resolved 809994ba84, whose -Cache run [42253517707](https://github.com/moq-dev/moq/actions/runs/42253517707) -finished at 16:46Z, after the build. #8114 pins both Smoke builds to the newest -`main` commit with a successful push Cache run, so the next scheduled run is a -direct test: any `building '...moq-relay-...drv'` line in that step is a real miss. - -## Waiting - -- moq-dev/moq: a scheduled Smoke run (08:00 UTC) whose `ubuntu-latest / nix` - job, after #8114 merges, copies `moq-relay` and `moq` from - `https://nix.moq.dev` instead of compiling them. Check with - `gh run list --workflow smoke.yml --event schedule`: its "Build moq from the - flake" step names the pinned commit, which already had a successful Cache run, - so a `building` line for either binary is a cache miss: rule out the bucket's - 30-day object expiry before calling it a cache bug. - -## Related - -- [CI cost and latency](/quest/m0/ci/README.md) - the R2 and Environment decisions this verifies