paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-09-10

Open
#531 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-10 (tag e2e-ci-nightly).

E2E Test Pass · ❌ FAIL

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

Cell Result Time
pr-deploy-foundry ❌ FAIL 2m00s
pr-install ❌ FAIL 1m59s
pr-deploy-cdm ❌ FAIL 2m30s
pr-mod ❌ FAIL 1m59s
nightly-deploy-moddable ❌ FAIL 2m01s
pr-preflight ❌ FAIL 2m02s
pr-deploy-frontend ❌ FAIL 2m09s
nightly-rejections ❌ FAIL 2m11s
nightly-diagnostic ❌ FAIL 1m59s
nightly-deploy-multi ❌ FAIL 1m59s
pr-login-session ❌ FAIL 1m59s
nightly-mod-miss ❌ FAIL 2m00s
nightly-deploy-hardhat ❌ FAIL 1m59s
nightly-chaos-sigint ❌ FAIL 2m13s
nightly-chaos-rpc ❌ FAIL 2m00s

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 run 34445604177 at commit 3428745, then inspect the linked Sentry spans filtered by e2e-ci-nightly. Compare the failures across the listed E2E cells to identify the common cause. Done means the affected nightly E2E cells pass again in a subsequent run.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.