[VL] Fix flaky columnar cache tests by clearing the cache serializer states before the suites are run#10812
Merged
zhztheplayer merged 2 commits intoapache:mainfrom Sep 26, 2025
Merged
Conversation
|
Run Gluten Clickhouse CI on x86 |
zhouyuan
approved these changes
Sep 26, 2025
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.
We should always call
InMemoryRelation.clearSerializer()for each Spark session that sets a new cache serializer.Failing to do this will cause flaky test results because whether the cache serializer is set to columnar or not is unclear when the test is run.
The patch fixes the issue.
Unblocks #10802.