paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-09-13

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

E2E Test Pass · ❌ FAIL

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

Cell Result Time
nightly-deploy-moddable ❌ FAIL 2m21s
pr-deploy-cdm ❌ FAIL 2m22s
pr-deploy-frontend ❌ FAIL 2m36s
pr-mod ❌ FAIL 2m22s
pr-deploy-foundry ✅ PASS 0m45s
nightly-rejections ✅ PASS 0m50s
nightly-chaos-rpc ✅ PASS 0m47s
pr-install ✅ PASS 0m54s
nightly-diagnostic ❌ FAIL 2m30s
pr-login-session ❌ FAIL 4m22s
nightly-chaos-sigint ❌ FAIL 2m20s
pr-preflight ❌ FAIL 2m32s
nightly-mod-miss ❌ FAIL 2m25s
nightly-deploy-multi ✅ PASS 0m42s
nightly-deploy-hardhat ✅ PASS 1m47s
❌ Failed tests (1)
  • e2e/cli/session.test.ts › session management > corrupted session file does not produce a valid signer
    expected +0 not to be +0 // Object.is equality

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 e2e/cli/session.test.ts and the linked GitHub Actions run for commit 3428745. Investigate the corrupted-session case and its expected signer assertion, then rerun the relevant E2E checks. Done means the test no longer accepts a valid signer from a corrupted session and the affected nightly checks pass.

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
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.