paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-08-19

Open
#507 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-08-19 (tag e2e-ci-nightly).

E2E Test Pass · ❌ FAIL

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

Cell Result Time
nightly-mod-miss ❌ FAIL 2m19s
pr-install ✅ PASS 0m47s
pr-deploy-frontend ❌ FAIL 2m52s
pr-deploy-cdm ✅ PASS 4m42s
nightly-deploy-multi ✅ PASS 0m43s
pr-deploy-foundry ✅ PASS 0m46s
nightly-diagnostic ❌ FAIL 2m29s
nightly-deploy-moddable ❌ FAIL 2m21s
nightly-chaos-rpc ✅ PASS 0m42s
nightly-chaos-sigint ❌ FAIL 2m17s
nightly-rejections ✅ PASS 0m47s
nightly-deploy-hardhat ✅ PASS 0m40s
pr-login-session ❌ FAIL 4m12s
pr-preflight ❌ FAIL 2m30s
pr-mod ❌ FAIL 2m54s

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 50bdd8b and compare the failed cells, including nightly-mod-miss, pr-deploy-frontend, and pr-preflight. Use the Sentry traces for this run to identify whether the failures share a cause; done means the affected E2E cells pass again in a subsequent nightly run.

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
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.