paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-08-20
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-20 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: 50bdd8b · Run logs
| Cell | Result | Time |
|---|---|---|
nightly-chaos-sigint |
❌ FAIL | 2m24s |
pr-deploy-foundry |
✅ PASS | 0m48s |
pr-install |
✅ PASS | 0m54s |
pr-preflight |
❌ FAIL | 2m36s |
pr-mod |
❌ FAIL | 2m24s |
nightly-chaos-rpc |
✅ PASS | 0m49s |
nightly-rejections |
✅ PASS | 0m41s |
nightly-deploy-multi |
✅ PASS | 1m39s |
nightly-mod-miss |
❌ FAIL | 2m11s |
nightly-deploy-moddable |
❌ FAIL | 2m26s |
pr-deploy-frontend |
❌ FAIL | 2m45s |
pr-deploy-cdm |
✅ PASS | 3m24s |
nightly-deploy-hardhat |
✅ PASS | 0m48s |
nightly-diagnostic |
❌ FAIL | 2m35s |
pr-login-session |
❌ FAIL | 4m46s |
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 run logs for commit 50bdd8b and compare the failing cells, especially nightly-chaos-sigint, pr-preflight, pr-mod, nightly-mod-miss, nightly-deploy-moddable, pr-deploy-frontend, nightly-diagnostic, and pr-login-session. Check the linked Sentry traces for this run. Done means the underlying failure is identified and the affected E2E cells pass in a subsequent nightly 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
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100