paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-07-23
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-23 (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 | 3m44s |
pr-deploy-frontend |
❌ FAIL | 3m00s |
pr-deploy-foundry |
✅ PASS | 0m53s |
nightly-diagnostic |
❌ FAIL | 2m24s |
nightly-deploy-moddable |
❌ FAIL | 2m38s |
nightly-mod-miss |
❌ FAIL | 2m38s |
pr-login-session |
❌ FAIL | 5m09s |
nightly-rejections |
✅ PASS | 0m45s |
pr-preflight |
❌ FAIL | 4m04s |
pr-mod |
❌ FAIL | 4m53s |
pr-install |
✅ PASS | 0m49s |
nightly-deploy-multi |
✅ PASS | 0m50s |
nightly-chaos-rpc |
✅ PASS | 0m50s |
nightly-chaos-sigint |
❌ FAIL | 2m26s |
nightly-deploy-hardhat |
✅ PASS | 0m46s |
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 linked GitHub Actions run logs for commit db851cc and compare the failed cells with the passing cells. Use the linked Sentry traces to identify the common failure, then reproduce the affected nightly E2E checks; done means the failing checks pass on 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
- 25/100