paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-06-16

Open
#394 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-06-16 (tag e2e-ci-nightly).

E2E Test Pass · ❌ FAIL

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

Cell Result Time
pr-deploy-cdm ✅ PASS 4m26s
nightly-diagnostic ❌ FAIL 2m13s
nightly-deploy-hardhat ✅ PASS 0m45s
pr-mod ❌ FAIL 3m18s
pr-install ✅ PASS 0m48s
nightly-mod-miss ✅ PASS 0m59s
pr-deploy-foundry ✅ PASS 0m55s
nightly-chaos-rpc ❌ FAIL 6m02s
nightly-chaos-sigint ❌ FAIL 5m57s
nightly-deploy-multi ✅ PASS 1m12s
nightly-rejections ✅ PASS 0m46s
pr-preflight ❌ FAIL 6m13s
pr-deploy-frontend ❌ FAIL 16m09s
pr-login-session ✅ PASS 1m55s
nightly-deploy-moddable ❌ FAIL 6m47s

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 a5e09ab and compare the failing cells: nightly-diagnostic, pr-mod, nightly-chaos-rpc, nightly-chaos-sigint, pr-preflight, pr-deploy-frontend, and nightly-deploy-moddable. Use the linked Sentry traces for additional context; done means the affected nightly E2E cells pass again.

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
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.