paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-09-18

Open
#539 0 comments 0 reactions 0 assignees View on GitHub

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-18 (tag e2e-ci-nightly).

E2E Test Pass · ❌ FAIL

Tag: e2e-ci-nightly · Branch: main · Commit: 3428745 · Run logs

Cell Result Time
pr-mod ❌ FAIL 2m20s
pr-login-session ❌ FAIL 4m24s
nightly-chaos-rpc ✅ PASS 0m45s
nightly-deploy-hardhat ✅ PASS 0m44s
nightly-deploy-multi ✅ PASS 0m42s
pr-deploy-foundry ✅ PASS 0m48s
nightly-mod-miss ❌ FAIL 2m25s
nightly-deploy-moddable ❌ FAIL 2m11s
nightly-diagnostic ❌ FAIL 2m18s
pr-deploy-cdm ❌ FAIL 2m47s
nightly-rejections ✅ PASS 0m47s
pr-install ✅ PASS 0m46s
pr-preflight ❌ FAIL 2m29s
nightly-chaos-sigint ❌ FAIL 2m18s
pr-deploy-frontend ❌ FAIL 2m47s

Sentry traces: view spans for this run

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the GitHub Actions run logs for commit 3428745 and the linked Sentry traces. Compare the failed cells—especially pr-mod, pr-login-session, nightly-mod-miss, nightly-deploy-moddable, nightly-diagnostic, pr-deploy-cdm, pr-preflight, nightly-chaos-sigint, and pr-deploy-frontend—with the passing cells. Done means identifying and fixing the shared cause so the nightly E2E run passes.

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
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.