Skip to content

ci(dogfood): prune the per-sha Turbo seed to the run's tasks before saving it #30241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 2 commits into from
Nov 5, 2026
+23 −2
Merged

ci(dogfood): prune the per-sha Turbo seed to the run's tasks before saving it #30241

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4f58391
ci(dogfood): prune the Turbo seed to the run's tasks before saving it
claude Nov 5, 2026
2a73776
Merge remote-tracking branch 'origin/main' into claude/issue-25452-do…
claude Nov 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 23 additions & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2536,10 +2536,13 @@ jobs:
# The build step above still builds the closure once, so the closure's
# `build` tasks REPLAY here (identical hashes: nothing run-level is
# hashed into them any more) and only `dogfood#test` executes.
# `--summarize` writes `.turbo/runs/<id>.json` and moves no task hash;
# it names the closure's `build` tasks and `dogfood#test` alike, and
# the prune before the seed save keeps exactly those entries.
export OS_TEST_SHARD="${{ matrix.shard }}/3"
node scripts/run-with-stall-guard.mjs --log "$RUNNER_TEMP/dogfood.log" --stall-minutes 10 \
--report-dir "$RUNNER_TEMP/stall-reports" -- \
pnpm turbo run test --filter=@objectstack/dogfood --log-order=stream
pnpm turbo run test --filter=@objectstack/dogfood --summarize --log-order=stream

# Test leftovers, step 2 of 2 (#23880, ruling 乙): what the dogfood test
# run added to the working tree. Report only -- exits 0 on every path, no
Expand Down Expand Up @@ -2574,10 +2577,28 @@ jobs:
if-no-files-found: ignore
retention-days: 14

# Keeps only the entries the test step's run summary (`.turbo/runs/`)
# names, as Test Core's prune step does (#25452): the restore step takes
# the newest seed by prefix and turbo never evicts its local cache, so a
# seed saved whole is every seed before it plus this run (~3.69 GB per
# seed in #25452's pool reading). That one summary names the whole
# closure -- the test run plans the closure step's `build` tasks with the
# same hashes -- so no `--extra-summaries` is needed, and the closure
# `upgrade-harness-optin.yml` restores this seed for stays in it. No
# summary -- the test step was cancelled or never ran -- means no save,
# and the previous seed stays the newest. Exits 0 on every run-time
# path, so it cannot withhold the attestation below.
- name: Prune the Turbo cache to this run's tasks (main only)
id: prune-turbo-cache
if: always() && github.event_name == 'push'
run: |
node scripts/ci/prune-turbo-cache.mjs --site 'Dogfood Regression Gate (${{ matrix.shard }}/3)' \
--cache .turbo/cache --run-summaries .turbo/runs

# Seed the shared Turbo cache from main only (see the restore step
# above); shard-scoped key so the two matrix jobs don't collide.
- name: Save Turbo cache (main only)
if: always() && github.event_name == 'push'
if: always() && github.event_name == 'push' && steps.prune-turbo-cache.outputs.save == 'true'
uses: actions/cache/save@v6
with:
path: .turbo/cache
Expand Down
Loading