paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-08-29

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

E2E Test Pass · ❌ FAIL

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

Cell Result Time
pr-login-session ❌ FAIL 4m26s
nightly-diagnostic ❌ FAIL 2m24s
pr-mod ❌ FAIL 2m21s
pr-install ✅ PASS 0m49s
nightly-deploy-moddable ❌ FAIL 2m08s
pr-deploy-foundry ✅ PASS 0m52s
nightly-deploy-hardhat ✅ PASS 0m40s
nightly-rejections ✅ PASS 0m47s
pr-preflight ❌ FAIL 2m28s
pr-deploy-cdm ❌ FAIL 2m23s
nightly-mod-miss ❌ FAIL 2m11s
nightly-chaos-sigint ❌ FAIL 2m35s
nightly-deploy-multi ✅ PASS 0m47s
pr-deploy-frontend ❌ FAIL 2m33s
nightly-chaos-rpc ✅ PASS 0m49s
❌ 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 inspect the failed registry-miss case, then use the linked GitHub Actions run logs to compare the expected message with the actual MetaRegistryFailure output. Check whether the related nightly failures share the same cause. Done means the affected E2E tests pass and the unknown-domain error includes the expected domain information.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, cli, testing
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.