Nightly E2E failure: 2026-08-13

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the linked GitHub Actions run logs for commit 50bdd8b and compare the failures across the e2e-ci-nightly cells. Use the linked Sentry traces to identify the common failure, then verify that the affected E2E cells pass again in a subsequent nightly run.

Written by the indexing model from the issue text.

Description

Nightly E2E failed on 2026-08-13 (tag e2e-ci-nightly).

E2E Test Pass · ❌ FAIL

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

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

Sentry traces: view spans for this run

Dominant language
TypeScript
Stars
5
Forks
12
No merged PRs in 30d

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.

More from paritytech/playground-cli

All issues in paritytech/playground-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.