paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-08-27
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-08-27 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: 3428745 · Run logs
| Cell | Result | Time |
|---|---|---|
nightly-rejections |
✅ PASS | 0m46s |
pr-deploy-foundry |
✅ PASS | 0m41s |
pr-preflight |
❌ FAIL | 2m28s |
nightly-diagnostic |
❌ FAIL | 2m21s |
nightly-deploy-multi |
✅ PASS | 0m42s |
pr-login-session |
❌ FAIL | 4m33s |
nightly-chaos-sigint |
❌ FAIL | 2m16s |
nightly-chaos-rpc |
✅ PASS | 0m51s |
pr-deploy-frontend |
❌ FAIL | 2m51s |
pr-mod |
❌ FAIL | 2m17s |
nightly-deploy-hardhat |
✅ PASS | 0m46s |
nightly-deploy-moddable |
❌ FAIL | 2m10s |
pr-deploy-cdm |
❌ FAIL | 2m27s |
pr-install |
✅ PASS | 0m48s |
nightly-mod-miss |
❌ 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 logs, focusing on the two failed dot mod tests and the MetaRegistryFailure. Compare the expected error text with the reported output and trace the registry lookup involved in the failure. Done means the affected nightly E2E tests pass with the intended registry behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, cli, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100