-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-31655][BUILD][3.0] Upgrade snappy-java to 1.1.7.5 #28509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think we can have a valid unit test case for this? (non-ppc64le part)
Test build #122532 has finished for PR 28509 at commit
|
BTW, currently, Jenkins jobs seems to be broken due to some outside issues. |
No wonder this strange mistake |
retest this please |
Test build #122542 has finished for PR 28509 at commit
|
This needs to go into master first, right? |
Has been merged into master Backport to 2.4 & 3.0 now. Seems jenkins have some problem |
Does test-dependencies.sh pass locally? I don't see any clear output here. |
Yeah, in local can pass it. |
Retest this please. |
Test build #122556 has finished for PR 28509 at commit
|
Do you know what happened? seems in master mvn is different from branch-3.0 and branch-2.4 In master's succes build
In branch 3.0 failed build
in Branch-2.4 failed build
|
In auto check, |
There is a network outage in the Jenkins farm. |
retest this please |
Test build #122602 has finished for PR 28509 at commit
|
FYI, the dependency failure will be fixed by the following. |
Retest this please. |
Test build #122652 has finished for PR 28509 at commit
|
retest this please |
Test build #122655 has finished for PR 28509 at commit
|
retest this please |
Test build #122725 has finished for PR 28509 at commit
|
@dongjoon-hyun Seems something still wrong, missing something on branch-3.0? |
Yes. |
BTW, the previous failed UT, |
Retest this please |
Hm, I wonder if |
Thank you for the tip. Yes. It's possible, but in a shared cluster, is it okay to purge it by one Maven job while the other Maven jobs are working? Maybe, we can enforce it at the specific single machine by recognizing the machine name because the machine seems to fail already always in any way. |
Hm, not sure. I think it's thread-safe. At least, if it doesn't work at all now, can't be much worse. This would not be merged, just a one-time thing. |
Got it. I'll try to make a PR to purge it. |
Test build #122728 has finished for PR 28509 at commit
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### What changes were proposed in this pull request? snappy-java have release v1.1.7.5, upgrade to latest version. Fixed in v1.1.7.4 - Caching internal buffers for SnappyFramed streams #234 - Fixed the native lib for ppc64le to work with glibc 2.17 (Previously it depended on 2.22) Fixed in v1.1.7.5 - Fixes java.lang.NoClassDefFoundError: org/xerial/snappy/pool/DefaultPoolFactory in 1.1.7.4 xerial/snappy-java@1.1.7.3...1.1.7.5 v 1.1.7.5 release note: xerial/snappy-java@edc4ec2 ### Why are the changes needed? Fix bug ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? No need Closes #28509 from AngersZhuuuu/SPARK-31655-3.0. Authored-by: angerszhu <angers.zhu@gmail.com> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
What changes were proposed in this pull request?
snappy-java have release v1.1.7.5, upgrade to latest version.
Fixed in v1.1.7.4
Fixed in v1.1.7.5
xerial/snappy-java@1.1.7.3...1.1.7.5
v 1.1.7.5 release note:
xerial/snappy-java@edc4ec2
Why are the changes needed?
Fix bug
Does this PR introduce any user-facing change?
No
How was this patch tested?
No need