paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-07-25
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-25 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: db851cc · Run logs
| Cell | Result | Time |
|---|---|---|
pr-deploy-cdm |
✅ PASS | 3m36s |
pr-preflight |
❌ FAIL | 2m54s |
pr-install |
✅ PASS | 0m52s |
pr-deploy-frontend |
❌ FAIL | 2m45s |
pr-mod |
❌ FAIL | 2m50s |
pr-deploy-foundry |
✅ PASS | 0m56s |
nightly-rejections |
✅ PASS | 0m42s |
nightly-diagnostic |
❌ FAIL | 2m38s |
nightly-deploy-hardhat |
✅ PASS | 0m48s |
nightly-chaos-sigint |
❌ FAIL | 2m49s |
nightly-chaos-rpc |
✅ PASS | 0m51s |
nightly-deploy-moddable |
❌ FAIL | 2m41s |
nightly-mod-miss |
❌ FAIL | 2m31s |
nightly-deploy-multi |
✅ PASS | 0m48s |
pr-login-session |
❌ FAIL | 4m23s |
❌ Failed tests (1)
e2e/cli/diagnostic.test.ts › diagnostic mode > DOT_DEPLOY_VERBOSE=1 produces timestamped log lines during storage phase
expected to reach availability check with verbose on ╭────────────────────────────────────────────────────────────────────────────╮ │ 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 '\n ╭────────────────────────────────…' to contain 'Checking availability'
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/diagnostic.test.ts and run the failing diagnostic-mode test against the nightly commit db851cc. Compare the test's expected availability check and timestamped verbose output with the run logs and the other failed cells. Done means the test reaches “Checking availability” with DOT_DEPLOY_VERBOSE=1 and passes reliably in the nightly E2E run.
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
- 58/100