paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-09-03

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

E2E Test Pass · ❌ FAIL

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

Cell Result Time
nightly-chaos-sigint ❌ FAIL 2m12s
pr-deploy-foundry ❌ FAIL 2m03s
pr-login-session ❌ FAIL 2m02s
pr-preflight ❌ FAIL 2m04s
pr-deploy-frontend ❌ FAIL 2m07s
pr-deploy-cdm ❌ FAIL 2m27s
nightly-rejections ❌ FAIL 2m06s
pr-mod ❌ FAIL 2m03s
nightly-chaos-rpc ❌ FAIL 2m04s
nightly-deploy-multi ❌ FAIL 2m10s
pr-install ❌ FAIL 1m58s
nightly-diagnostic ❌ FAIL 2m02s
nightly-deploy-moddable ❌ FAIL 2m06s
nightly-deploy-hardhat ❌ FAIL 2m02s
nightly-mod-miss ❌ FAIL 1m59s

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 linked GitHub Actions run logs for commit 3428745 and the Sentry traces filtered by e2e-ci-nightly. Compare the failures across the listed E2E cells to identify their common cause, then rerun the affected cells and confirm the nightly suite passes.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.