paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-07-29

Open
#478 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-07-29 (tag e2e-ci-nightly).

E2E Test Pass · ❌ FAIL

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

Cell Result Time
nightly-deploy-hardhat ✅ PASS 0m42s
pr-deploy-frontend ❌ FAIL 2m46s
pr-deploy-cdm ✅ PASS 3m56s
nightly-chaos-sigint ❌ FAIL 2m29s
nightly-diagnostic ❌ FAIL 2m23s
nightly-mod-miss ❌ FAIL 2m21s
pr-deploy-foundry ✅ PASS 0m47s
pr-install ✅ PASS 0m46s
nightly-chaos-rpc ✅ PASS 0m48s
nightly-rejections ✅ PASS 0m46s
pr-mod ❌ FAIL 2m34s
pr-preflight ❌ FAIL 2m36s
nightly-deploy-moddable ❌ FAIL 2m43s
nightly-deploy-multi ✅ PASS 0m44s
pr-login-session ❌ FAIL 4m18s
❌ 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, especially the test for a corrupted session file, then inspect the linked nightly run logs for the failing assertion. Reproduce the failure and trace why the test reports expected +0 not to be +0; done means the corrupted-session case passes consistently in the E2E suite.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.