paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-08-28
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-28 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: 3428745 · Run logs
| Cell | Result | Time |
|---|---|---|
pr-deploy-frontend |
❌ FAIL | 2m57s |
pr-deploy-foundry |
✅ PASS | 0m42s |
pr-preflight |
❌ FAIL | 2m42s |
nightly-diagnostic |
❌ FAIL | 2m25s |
pr-login-session |
❌ FAIL | 4m22s |
nightly-deploy-multi |
✅ PASS | 0m51s |
nightly-deploy-hardhat |
✅ PASS | 0m48s |
nightly-chaos-sigint |
❌ FAIL | 2m22s |
nightly-deploy-moddable |
❌ FAIL | 2m21s |
pr-mod |
❌ FAIL | 2m21s |
nightly-mod-miss |
❌ FAIL | 2m28s |
pr-deploy-cdm |
❌ FAIL | 2m30s |
nightly-chaos-rpc |
✅ PASS | 0m48s |
pr-install |
✅ PASS | 0m48s |
nightly-rejections |
✅ PASS | 1m07s |
❌ Failed tests (3)
e2e/cli/deploy.test.ts › dot deploy --playground — full pipeline (requires Paseo + IPFS) > frontend-only deploy completes end-to-end
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 registrye2e/cli/deploy.test.ts › dot deploy --playground — full pipeline (requires Paseo + IPFS) > re-deploy same domain succeeds for same owner
expected '\n ╭────────────────────────────────…' to contain 'Deploy complete'e2e/cli/deploy.test.ts › dot deploy --playground — full pipeline (requires Paseo + IPFS) > domain taken by another account shows unavailable
bob deploy unexpectedly succeeded: ╭────────────────────────────────────────────────────────────────────────────╮ │ Join the competition first │ │ Playground commands are for builders who've joined the competition, so you │ │ need to be signed in first. │ │ │ │ Runplayground loginand scan the QR code with your Polkadot mobile app, │ │ then become a builder and join the competition at playground.dot in your │ │ desktop app. │ ╰────────────────────────────────────────────────────────────────────────────╯ : expected +0 not to be +0 // Object.is equality
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 the failed cases in e2e/cli/deploy.test.ts and inspect the linked GitHub Actions run logs for commit 3428745. Determine why registry resolution, redeployment, and the account/session checks fail; done means the affected nightly E2E cells pass without regressing the already passing cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, cli, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100