paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-08-24
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-24 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: 3428745 · Run logs
| Cell | Result | Time |
|---|---|---|
pr-deploy-cdm |
✅ PASS | 3m38s |
nightly-deploy-hardhat |
✅ PASS | 0m48s |
nightly-mod-miss |
❌ FAIL | 2m14s |
nightly-chaos-rpc |
✅ PASS | 0m45s |
nightly-deploy-moddable |
❌ FAIL | 2m11s |
pr-login-session |
❌ FAIL | 4m33s |
nightly-diagnostic |
❌ FAIL | 2m29s |
pr-install |
✅ PASS | 0m46s |
pr-mod |
❌ FAIL | 2m24s |
pr-preflight |
❌ FAIL | 2m30s |
nightly-deploy-multi |
✅ PASS | 0m42s |
nightly-rejections |
✅ PASS | 0m38s |
nightly-chaos-sigint |
❌ FAIL | 2m21s |
pr-deploy-frontend |
❌ FAIL | 3m09s |
pr-deploy-foundry |
✅ PASS | 0m42s |
❌ Failed tests (1)
e2e/cli/deploy.test.ts › dot deploy — preflight and validation > domain availability check runs before build/upload
availability banner not found: ╭────────────────────────────────────────────────────────────────────────────╮ │ 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 -1 to be greater than -1
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/deploy.test.ts and the linked run logs for the failing dot deploy preflight test. Compare the expected domain-availability banner with the observed sign-in message and trace where that output is produced. Done means the test reliably finds the availability banner while the other reported E2E checks remain passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100