paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-09-15

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

E2E Test Pass · ❌ FAIL

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

Cell Result Time
nightly-deploy-hardhat ✅ PASS 0m46s
nightly-chaos-rpc ✅ PASS 0m51s
pr-deploy-frontend ❌ FAIL 2m37s
pr-deploy-foundry ✅ PASS 0m40s
nightly-diagnostic ❌ FAIL 2m25s
nightly-deploy-multi ✅ PASS 0m48s
nightly-rejections ✅ PASS 0m42s
pr-deploy-cdm ❌ FAIL 2m50s
nightly-chaos-sigint ❌ FAIL 2m17s
nightly-mod-miss ❌ FAIL 2m12s
pr-mod ❌ FAIL 2m44s
pr-preflight ❌ FAIL 2m23s
nightly-deploy-moddable ❌ FAIL 2m09s
pr-login-session ❌ FAIL 4m15s
pr-install ✅ PASS 0m46s

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 compare the failing cells, especially pr-deploy-frontend, nightly-diagnostic, pr-deploy-cdm, and pr-login-session, with the passing cells. Trace the first common failure and reproduce the affected E2E flow; done means the failing cells pass in a new 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
Active
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.