paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-09-16
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Nightly E2E failed on 2026-09-16 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: 3428745 · Run logs
| Cell | Result | Time |
|---|---|---|
nightly-rejections |
✅ PASS | 0m40s |
pr-login-session |
❌ FAIL | 4m24s |
nightly-chaos-sigint |
❌ FAIL | 2m43s |
nightly-diagnostic |
❌ FAIL | 2m17s |
pr-deploy-cdm |
❌ FAIL | 3m17s |
nightly-mod-miss |
❌ FAIL | 2m17s |
pr-install |
✅ PASS | 0m45s |
nightly-chaos-rpc |
✅ PASS | 0m44s |
pr-preflight |
❌ FAIL | 2m26s |
pr-deploy-foundry |
✅ PASS | 0m45s |
pr-deploy-frontend |
❌ FAIL | 2m48s |
nightly-deploy-hardhat |
✅ PASS | 0m43s |
pr-mod |
❌ FAIL | 2m16s |
nightly-deploy-multi |
✅ PASS | 0m41s |
nightly-deploy-moddable |
❌ FAIL | 2m16s |
❌ Failed tests (2)
e2e/cli/mod.test.ts › dot mod — clone > full clone flow: fetches source, runs setup.sh, writes dot.json
mod failed: MetaRegistryFailure: Could not resolve the live Playground registry contract address from the CDM meta-registry. Refusing to use the cdm.json snapshot because it may be stale. Contract "@w3s/playground-registry" is not registered in the CDM registry: expected 1 to be +0 // Object.is equalitye2e/cli/mod.test.ts › dot mod — clone > exits non-zero for unknown domain with no prior session (mod is signer-less)
expected '\nMetaRegistryFailure: Could not reso…' to contain 'not found in registry'
Sentry traces: view spans for this run
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with e2e/cli/mod.test.ts and the linked GitHub Actions run, focusing on the MetaRegistryFailure for @w3s/playground-registry. Trace why the live CDM registry lookup fails and confirm the affected E2E cases pass without using a stale snapshot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100