paritytech / paritytech/playground-cli
Nightly E2E failure: 2026-07-13
Open
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-13 (tag e2e-ci-nightly).
E2E Test Pass · ❌ FAIL
Tag: e2e-ci-nightly · Branch: main · Commit: db851cc · Run logs
| Cell | Result | Time |
|---|---|---|
pr-deploy-cdm |
✅ PASS | 3m50s |
nightly-rejections |
✅ PASS | 0m50s |
nightly-diagnostic |
❌ FAIL | 2m32s |
nightly-mod-miss |
❌ FAIL | 2m57s |
pr-install |
✅ PASS | 0m50s |
pr-deploy-foundry |
✅ PASS | 0m51s |
pr-deploy-frontend |
❌ FAIL | 2m56s |
nightly-deploy-hardhat |
✅ PASS | 0m53s |
pr-preflight |
❌ FAIL | 2m47s |
nightly-deploy-moddable |
❌ FAIL | 2m51s |
pr-login-session |
❌ FAIL | 4m43s |
nightly-chaos-rpc |
✅ PASS | 0m53s |
pr-mod |
❌ FAIL | 2m59s |
nightly-chaos-sigint |
❌ FAIL | 2m57s |
nightly-deploy-multi |
✅ PASS | 0m47s |
❌ Failed tests (1)
e2e/cli/deploy.test.ts › dot deploy — moddable (requires Paseo + IPFS + GH) > --moddable deploy stamps origin URL into registry metadata
expected '\n ╭────────────────────────────────…' to contain 'Deploy complete'
Sentry traces: view spans for this run
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with e2e/cli/deploy.test.ts and the failing dot deploy — moddable case, then inspect the linked GitHub Actions run logs for commit db851cc. Reproduce the Paseo, IPFS, and GitHub-dependent test and determine why the output does not contain Deploy complete; done means the nightly moddable deployment test passes with the expected output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100