paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-08-15
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-15 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: 50bdd8b · Run logs
| Cell | Result | Time |
|---|---|---|
pr-deploy-foundry |
✅ PASS | 0m42s |
nightly-mod-miss |
❌ FAIL | 2m16s |
nightly-rejections |
✅ PASS | 0m39s |
nightly-deploy-multi |
✅ PASS | 0m40s |
pr-deploy-cdm |
✅ PASS | 3m18s |
pr-login-session |
❌ FAIL | 4m11s |
nightly-deploy-hardhat |
✅ PASS | 0m43s |
pr-install |
✅ PASS | 0m45s |
pr-deploy-frontend |
❌ FAIL | 2m53s |
nightly-chaos-rpc |
✅ PASS | 0m46s |
nightly-deploy-moddable |
❌ FAIL | 2m55s |
pr-mod |
❌ FAIL | 2m15s |
nightly-diagnostic |
❌ FAIL | 3m13s |
nightly-chaos-sigint |
❌ FAIL | 2m35s |
pr-preflight |
❌ FAIL | 2m31s |
❌ 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 the linked GitHub Actions run logs for commit 50bdd8b. Investigate why the diagnostic-mode test reaches the sign-in message instead of the availability check, then confirm the expected timestamped verbose output and the affected nightly cells pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100