paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-07-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-07-16 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: db851cc · Run logs
| Cell | Result | Time |
|---|---|---|
pr-deploy-cdm |
❌ FAIL | 2m25s |
pr-deploy-foundry |
✅ PASS | 0m43s |
nightly-chaos-sigint |
❌ FAIL | 2m33s |
nightly-deploy-moddable |
❌ FAIL | 2m26s |
pr-mod |
❌ FAIL | 2m51s |
nightly-deploy-hardhat |
✅ PASS | 0m49s |
nightly-mod-miss |
❌ FAIL | 2m27s |
nightly-diagnostic |
❌ FAIL | 2m29s |
pr-install |
✅ PASS | 0m53s |
nightly-chaos-rpc |
✅ PASS | 0m50s |
nightly-rejections |
✅ PASS | 0m50s |
pr-login-session |
❌ FAIL | 4m31s |
pr-deploy-frontend |
❌ FAIL | 2m51s |
pr-preflight |
❌ FAIL | 2m52s |
nightly-deploy-multi |
✅ PASS | 0m50s |
❌ Failed tests (2)
e2e/cli/deploy.test.ts › dot deploy — preflight and validation > reports mainnet not yet supported
expected non-zero exit for --env mainnet, got 0 ╭────────────────────────────────────────────────────────────────────────────╮ │ 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 equalitye2e/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 inspect the failed preflight and domain-availability cases against the nightly run logs for commit db851cc. Reproduce the failures in the E2E suite, then verify that the mainnet validation and availability banner assertions pass without regressing the other deploy checks.
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
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100