Repository navigation
Give the S4 lint-clean module sweep a 60 s timeout so the Release runner does not time it out - #82
Merged
Merged
Conversation
…ner does not time it out Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
krijnrijshouwer
added a commit
that referenced
this pull request
Oct 5, 2026
…ner does not time it out (#82)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Release workflow on `main` has failed on both pushes since #79 merged (runs 37303735151 and 37303807332), so changesets could not refresh the Version Packages PR (#78).
Both failures are the same test: `no-selection-timers (S4) > the real in-config module-list sources lint clean as committed` in `packages/tooling/eslint-plugin`. It runs the S4 rule over every selection module in a single test, which took 12.0 s and 12.9 s on the Release runner against Vitest's 10 s default. The rule found nothing: the run timed out before the lint finished.
This gives that one test a 60 s timeout, the same per-test pattern already used for the slow properties in core (`documentState.childOrder`) and pen-dom (`blockNotifier.ax1Routes`). No other test without its own timeout came within 3 s of the default in the Release run.
`@input/pen-eslint-plugin` is private, so there is no changeset.
🤖 Generated with Claude Code