Skip to content

ci(try-runtime): test staging path (do not merge)#704

Draft
jaxter03 wants to merge 8 commits into
stagingfrom
feat/try-runtime-snapshot-caching
Draft

ci(try-runtime): test staging path (do not merge)#704
jaxter03 wants to merge 8 commits into
stagingfrom
feat/try-runtime-snapshot-caching

Conversation

@jaxter03
Copy link
Copy Markdown
Contributor

Summary

Draft PR to validate check-try-runtime.yaml against the staging base — exercises the testnet snapshot path + cere-runtime build.

Not for merge — same content as the dev-targeted PR being prepared.

Test plan

  • check-try-runtime job triggers on this PR with base_ref=staging
  • Restores try-runtime-snap-testnet-* from cache (warm)
  • Builds cere-runtime package only (not cere-dev-runtime)
  • Runs try-runtime on-runtime-upgrade snap --path (not live)
  • Total runtime well under the previous multi-hour live check

🤖 Generated with Claude Code

jaxter03 and others added 8 commits May 19, 2026 19:55
Split try-runtime check out of ci.yaml so it fires only on PRs into
dev (devnet/cere-dev-runtime) or staging (testnet/cere-runtime), with
per-PR concurrency cancellation and a path filter to skip non-runtime
PRs.

Add a daily snapshot workflow that pulls devnet and testnet state via
try-runtime create-snapshot and stores them in the Actions cache keyed
by date. The check workflow restores the latest snapshot and runs the
on-runtime-upgrade check against snap --path, falling back to live if
no snapshot is cached yet. The try-runtime-cli binary is also cached
across runs to skip the ~3-5 min cargo install.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Will be removed before merging to dev.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
try-runtime-cli's litep2p dep needs protoc at build time; without it
cargo install fails with "Could not find protoc".

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…tion

Will be removed before merging to dev.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
try-runtime refuses to run on-runtime-upgrade unless spec_version is
bumped vs the snapshot. For CI sanity checks (which run on branches
that often don't bump spec_version) we want the check to execute
regardless — same intent as the existing --disable-idempotency-checks.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Snapshots from 2026-05-19 were evicted from the Actions cache by the
10 GB LRU policy (cargo build caches outweighed them). Touching the
snapshot workflow file to re-fire its push trigger and repopulate.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant