[Pipe] Relax flaky TsFile event test timeouts - #18332
Merged
jt2594838 merged 1 commit intoJul 29, 2026
Merged
Conversation
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
2 participants
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.
Description
The Windows DataNode unit-test job can run under heavy memory and CPU pressure.
PipeTsFileInsertionEventAdmissionTesthad a 10-second whole-method timeout, and the observed failure timed out on the firstCommonDescriptor.getInstance()call during class initialization, before the parser-admission logic ran. The same JVM also reportedOutOfMemoryError: Java heap spacefrom Surefire's stream flusher.Raise the outer safety timeout to 60 seconds for the two Pipe TsFile event tests that used 5/10-second whole-method limits. The admission test's behavior checks remain strict and unchanged: it still verifies the parser stays blocked for 200 ms and resumes within 3 seconds after memory is released.
Verification
git diff --check: passedThe local targeted Maven run was blocked during reactor compilation because the installed Thrift 0.14.1 compiler generates
javax.annotation.Generatedsources on JDK 17. The PR CI uses the supported build environment and will provide the test result.