paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-09-07
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-09-07 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: 3428745 · Run logs
| Cell | Result | Time |
|---|---|---|
pr-deploy-cdm |
❌ FAIL | 2m30s |
nightly-mod-miss |
❌ FAIL | 2m07s |
pr-deploy-foundry |
❌ FAIL | 2m03s |
pr-deploy-frontend |
❌ FAIL | 2m06s |
pr-login-session |
❌ FAIL | 2m06s |
pr-preflight |
❌ FAIL | 2m03s |
nightly-rejections |
❌ FAIL | 2m03s |
nightly-diagnostic |
❌ FAIL | 2m02s |
nightly-deploy-moddable |
❌ FAIL | 2m15s |
nightly-deploy-multi |
❌ FAIL | 2m01s |
nightly-deploy-hardhat |
❌ FAIL | 2m05s |
pr-install |
❌ FAIL | 2m00s |
nightly-chaos-sigint |
❌ FAIL | 2m03s |
nightly-chaos-rpc |
❌ FAIL | 2m08s |
pr-mod |
❌ FAIL | 2m02s |
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 for commit 3428745 and compare the failures across the listed E2E cells. Use the Sentry trace link to find the shared failure, then identify the affected workflow or test entry point. Done means the underlying failure is fixed and the nightly E2E cells pass on a rerun.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100