[SPARK-53162][SQL][TESTS] Mark DynamicPartitionPruningHive*Suite* as SlowHiveTest
#51888
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
dongjoon-hyun
force-pushed
the
SPARK-53162
branch
from
53840af to
0dd5580
Compare
dongjoon-hyun
changed the title
DynamicPartitionPruning*Suite* as SlowHiveTestDynamicPartitionPruningHive*Suite* as SlowHiveTest
Member
Author
|
Since Hive CIs finished already, I updated the PR description. |
Member
Author
|
All tests passed. Could you review this PR, @LuciferYang ? |
yaooqinn
approved these changes
Aug 7, 2025
LuciferYang
approved these changes
Aug 7, 2025
Member
Author
|
Thank you, @yaooqinn and @LuciferYang . Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What changes were proposed in this pull request?
This PR aims to mark
DynamicPartitionPruningHive*Suite*asSlowHiveTest.Why are the changes needed?
To balance Hive CIs.
BEFORE (master branch)
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Check the CI result on this PR.
Was this patch authored or co-authored using generative AI tooling?
No.