paritytech / paritytech/playground-cli

Nightly E2E failures — root cause investigation

Open
#241 1 comment 0 reactions 1 assignee View on GitHub

@UtkarshBhardwaj007 is already working on this.

Since Jun 3, 2026.

bug CLI P0 V1
Dominant language
TypeScript
Stars
5
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Centralised tracker for recurring nightly E2E failures. Replaces the per-night auto-filed issues (each was a new card on the kanban, no signal in the pattern).

Recent failed nightlies

Date Commit Notable failing cells
2026-05-26 17890c5 nightly-deploy-moddable
2026-05-28 3a670f8 pr-preflight, pr-deploy-foundry, pr-deploy-cdm
2026-05-29 3a670f8 nightly-mod-miss
2026-05-30 5e3a88a pr-mod
2026-05-31 5e3a88a pr-deploy-frontend (13m34s — likely timeout)
2026-06-01 5e3a88a (see closed #234)
2026-06-02 306964c (see closed #237)
2026-06-03 306964c pr-mod

Recurring cells: pr-mod, pr-deploy-frontend, nightly-deploy-moddable. Suggests one or two underlying regressions rather than 8 distinct bugs.

TODOs

  • Investigate the recurring pr-mod and pr-deploy-* failures — likely one root cause.
  • Update the auto-filing workflow to comment on this issue rather than spawn a new one each night. That's why we ended up with 8 cards on the board.

Replaces

Closed as duplicates: #207, #227, #228, #232, #233, #234, #237, #239.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.