[SPARK-47940][BUILD][TESTS] Upgrade guava dependency to 33.1.0-jre in Docker IT
#46167
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-47940
branch
from
5bd2ca3 to
31f1e88
Compare
Member
Author
|
I made this PR with your authorship, @pan3793 . |
6 tasks
Member
Author
|
|
Member
Author
|
Could you review this dependency PR, @huaxingao ? |
huaxingao
approved these changes
Apr 22, 2024
Contributor
huaxingao
left a comment
huaxingao
left a comment
There was a problem hiding this comment.
LGTM. Thanks for the PR @dongjoon-hyun
Member
Author
|
Thank you! Merged to master. |
Member
|
thank you, @dongjoon-hyun |
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 upgrade
guavadependency to33.1.0-jrein Docker Integration tests.Why are the changes needed?
This is a preparation of the following PR.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.