paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-07-22

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

E2E Test Pass · ❌ FAIL

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

Cell Result Time
pr-deploy-frontend ❌ FAIL 2m48s
pr-deploy-foundry ✅ PASS 0m43s
nightly-deploy-multi ✅ PASS 0m46s
nightly-deploy-hardhat ✅ PASS 0m50s
pr-deploy-cdm ✅ PASS 3m46s
nightly-mod-miss ❌ FAIL 2m25s
pr-install ✅ PASS 0m47s
pr-login-session ❌ FAIL 4m24s
pr-preflight ❌ FAIL 2m45s
nightly-diagnostic ❌ FAIL 2m22s
nightly-deploy-moddable ❌ FAIL 2m27s
pr-mod ❌ FAIL 2m30s
nightly-rejections ✅ PASS 0m45s
nightly-chaos-rpc ✅ PASS 0m49s
nightly-chaos-sigint ❌ FAIL 2m25s
❌ Failed tests (2)
  • e2e/cli/mod.test.ts › dot mod — clone > full clone flow: fetches source, runs setup.sh, writes dot.json
    expected [] to have a length of 1 but got +0
  • e2e/cli/mod.test.ts › dot mod — clone > exits non-zero for unknown domain with no prior session (mod is signer-less)
    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/mod.test.ts and the linked GitHub Actions run logs for commit db851cc. Investigate the two reported failures in the dot mod clone flow and the unknown-domain case. Done means both tests pass and the nightly E2E run no longer reports these failures.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.