paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-09-14

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

E2E Test Pass · ❌ FAIL

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

Cell Result Time
nightly-mod-miss ❌ FAIL 2m16s
pr-install ✅ PASS 0m51s
nightly-diagnostic ❌ FAIL 2m23s
pr-deploy-foundry ✅ PASS 0m41s
pr-login-session ❌ FAIL 4m19s
pr-mod ❌ FAIL 2m34s
pr-deploy-cdm ❌ FAIL 2m26s
nightly-deploy-moddable ❌ FAIL 2m12s
nightly-chaos-rpc ✅ PASS 0m46s
nightly-chaos-sigint ❌ FAIL 2m17s
nightly-deploy-hardhat ✅ PASS 0m41s
pr-preflight ❌ FAIL 2m27s
nightly-rejections ✅ PASS 0m40s
nightly-deploy-multi ✅ PASS 0m45s
pr-deploy-frontend ❌ FAIL 2m37s
❌ Failed tests (1)
  • e2e/cli/mod.test.ts › dot mod — registry miss > reports a registry-miss for an unknown domain
    expected '\nMetaRegistryFailure: Could not reso…' to contain 'nonexistent-domain-xyz-12345.paseo'

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 failing “dot mod — registry miss” test, then inspect the linked run logs for the full MetaRegistryFailure output. Reproduce the nightly failure and trace the registry-miss handling; done means the test correctly reports the unknown domain and the affected E2E checks pass.

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
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.