fix(test): declare per-test timeouts for dag-node-supervision long tests - #385
Merged
Conversation
LeXwDeX
marked this pull request as ready for review
August 19, 2026 21:40
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Summary
dispose-instance,cancel-defect,freeze window) need 12-15s by design but relied on a comment-only contract to be run with--timeout 30000. Bare focused invocation hit bun's default 5s per-test timeout and red-failed three healthy tests.it(..., 30000)per-test timeouts on the three tests and syncs the header comment.Verification
bun test test/dag/dag-node-supervision.test.ts(bare, previously 8 pass / 3 fail) → 11 pass / 0 fail--timeout 30000) unchanged green; file lints 0 warningsCloses#384