W-23530974: Skip slow big_intersection TCK case#138
Open
mlischetti wants to merge 1 commit into
Open
Conversation
The Windows CI runner failed on big_intersection: a 500-way intersection type stress case. It passes functionally but is pathologically slow — ~13s on a fast local machine, ~34s on the Windows runner, exceeding the tck project's 30s testTimeout. It was passing on macOS/Linux only because they're fast enough. Add it to the ignore list as a slow case, matching the CLI's TCKCliTest, which ignores it under "Take too long time" alongside array-concat and runtime_run. TCK lane: 659 passing, 58 skipped, 0 failures. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Fixes the remaining Windows-only TCK failure after #136.
big_intersection(a 500-way intersection type stress case) passes functionally but is pathologically slow — ~13s locally, ~34s on the Windows CI runner, exceeding the tck project's 30stestTimeout. It passed on macOS/Linux only because they're fast enough.Add it to the ignore list as a slow case, matching the CLI's
TCKCliTest, which ignores it under "Take too long time" (alongsidearray-concat,runtime_run).Testing
npm run test:tck→ 659 passed, 58 skipped, 0 failurestsc --noEmitclean🤖 Generated with Claude Code