HBASE-30382: Update zstd-jni to 1.5.7-15 - #8652
Open
arvindKandpal-ksolves wants to merge 1 commit into
Open
arvindKandpal-ksolves wants to merge 1 commit into
arvindKandpal-ksolves wants to merge 1 commit into
Conversation
arvindKandpal-ksolves
force-pushed
the
HBASE-30382
branch
from
September 16, 2026 06:35
f526909 to
69fc617
Compare
Contributor
Author
|
I guess this is Flakes test fail ? Can anyone help me here ? |
Contributor
Good question. Unfortunately sometimes there are flakey tests. If you open the failing check and click on the Summary tab then you can see which tests failed. |
Contributor
Author
|
Hi @PDavid, thanks for looking into this. I ran all 35 failing tests locally on this branch (JDK17, matching CI) and they all pass — confirms these are pre-existing flaky tests, unrelated to the zstd-jni bump. see here : |
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
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?
Bumps zstd-jni from 1.5.7-2 to 1.5.7-15 in the root pom.xml.
Why are the changes needed?
zstd-jni versions prior to 1.5.7-14 contain vulnerable code addressed by:
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Ran the full zstd-jni compression test suite before and after the bump:
TestWALCompressionZstd, TestZstdCodec, TestHFileCompressionZstd,
TestZstdDictionary, TestZstdDictionarySplitMerge, TestZstdByteBuffDecompressor.
Baseline (1.5.7-2): 15 tests run, 0 failures, 0 errors
After bump (1.5.7-15): 15 tests run, 0 failures, 0 errors
Also verified via
mvn dependency:treethat the resolved artifact iscom.github.luben:zstd-jni:jar:1.5.7-15.