paritytech / paritytech/playground-cli

Nightly E2E failure: 2026-08-04

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

E2E Test Pass · ❌ FAIL

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

Cell Result Time
pr-deploy-cdm ✅ PASS 4m08s
nightly-deploy-moddable ❌ FAIL 2m27s
pr-deploy-foundry ✅ PASS 0m41s
nightly-deploy-hardhat ✅ PASS 0m51s
pr-deploy-frontend ❌ FAIL 3m02s
pr-install ✅ PASS 0m53s
nightly-deploy-multi ✅ PASS 0m49s
pr-mod ❌ FAIL 2m41s
nightly-mod-miss ❌ FAIL 2m34s
nightly-chaos-sigint 🚫 CANCEL 0m24s
nightly-chaos-rpc ✅ PASS 0m50s
nightly-diagnostic ❌ FAIL 2m36s
pr-login-session ❌ FAIL 4m25s
nightly-rejections ✅ PASS 0m48s
pr-preflight ❌ FAIL 2m52s
❌ Failed tests (3)
  • e2e/cli/deploy.test.ts › dot deploy --playground — full pipeline (requires Paseo + IPFS) > frontend-only deploy completes end-to-end
    expected '\n ╭────────────────────────────────…' to contain 'Deploy complete'
  • e2e/cli/deploy.test.ts › dot deploy --playground — full pipeline (requires Paseo + IPFS) > re-deploy same domain succeeds for same owner
    expected '\n ╭────────────────────────────────…' to contain 'Deploy complete'
  • e2e/cli/deploy.test.ts › dot deploy --playground — full pipeline (requires Paseo + IPFS) > domain taken by another account shows unavailable
    bob deploy unexpectedly succeeded: ╭────────────────────────────────────────────────────────────────────────────╮ │ Join the competition first │ │ Playground commands are for builders who've joined the competition, so you │ │ need to be signed in first. │ │ │ │ Run playground login and scan the QR code with your Polkadot mobile app, │ │ then become a builder and join the competition at playground.dot in your │ │ desktop app. │ ╰────────────────────────────────────────────────────────────────────────────╯ : 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 the linked GitHub Actions run logs and the failed cases in e2e/cli/deploy.test.ts. Reproduce the frontend-only, same-domain, and cross-account deployment failures, then trace the relevant E2E behavior. Done means the listed failures pass without regressing the other nightly checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.