-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-32150][BUILD] Upgrade to ZStd 1.4.5-4 #28969
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
|
Test build #124805 has finished for PR 28969 at commit
|
|
Looks okay to me. cc: @dongjoon-hyun @srowen |
|
Looks OK to backport to 3.0.x right? |
|
branch-3.0 still uses zstd v1.4.4 because we didn't merge the last zstd upgrade commit (#28682) into branch-3.0. // zstd version in branch-3.0 Line 668 in bdbfe6e
If there is no compatiblity issue and the fixes are somewhat critical, I think merging this into branch-3.0 looks fine. |
|
Test build #124821 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #124843 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #124844 has finished for PR 28969 at commit
|
|
Test build #124845 has finished for PR 28969 at commit
|
dongjoon-hyun
left a comment
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.
+1, LGTM.
|
Test build #124914 has finished for PR 28969 at commit
|
|
Test build #124918 has finished for PR 28969 at commit
|
|
retest this please |
1 similar comment
|
retest this please |
|
Test build #124934 has started for PR 28969 at commit |
|
retest this please |
|
Test build #125041 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125062 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125069 has started for PR 28969 at commit |
|
Test build #125133 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125154 has finished for PR 28969 at commit
|
### What changes were proposed in this pull request? This PR aims to disable SBT `unidoc` generation testing in Jenkins environment because it's flaky in Jenkins environment and not used for the official documentation generation. Also, GitHub Action has the correct test coverage for the official documentation generation. - #28848 (comment) (amp-jenkins-worker-06) - #28926 (comment) (amp-jenkins-worker-06) - #28969 (comment) (amp-jenkins-worker-06) - #28975 (comment) (amp-jenkins-worker-05) - #28986 (comment) (amp-jenkins-worker-05) - #28992 (comment) (amp-jenkins-worker-06) - #28993 (comment) (amp-jenkins-worker-05) - #28999 (comment) (amp-jenkins-worker-04) - #29010 (comment) (amp-jenkins-worker-03) - #29013 (comment) (amp-jenkins-worker-04) - #29016 (comment) (amp-jenkins-worker-05) - #29025 (comment) (amp-jenkins-worker-04) - #29042 (comment) (amp-jenkins-worker-03) ### Why are the changes needed? Apache Spark `release-build.sh` generates the official document by using the following command. - https://github.com/apache/spark/blob/master/dev/create-release/release-build.sh#L341 ```bash PRODUCTION=1 RELEASE_VERSION="$SPARK_VERSION" jekyll build ``` And, this is executed by the following `unidoc` command for Scala/Java API doc. - https://github.com/apache/spark/blob/master/docs/_plugins/copy_api_dirs.rb#L30 ```ruby system("build/sbt -Pkinesis-asl clean compile unidoc") || raise("Unidoc generation failed") ``` However, the PR builder disabled `Jekyll build` and instead has a different test coverage. ```python # determine if docs were changed and if we're inside the amplab environment # note - the below commented out until *all* Jenkins workers can get `jekyll` installed # if "DOCS" in changed_modules and test_env == "amplab_jenkins": # build_spark_documentation() ``` ``` Building Unidoc API Documentation ======================================================================== [info] Building Spark unidoc using SBT with these arguments: -Phadoop-3.2 -Phive-2.3 -Pspark-ganglia-lgpl -Pkubernetes -Pmesos -Phadoop-cloud -Phive -Phive-thriftserver -Pkinesis-asl -Pyarn unidoc ``` ### Does this PR introduce _any_ user-facing change? No. (This is used only for testing and not used in the official doc generation.) ### How was this patch tested? Pass the Jenkins without doc generation invocation. Closes #29017 from dongjoon-hyun/SPARK-DOC-GEN. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
|
Test build #125396 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125418 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125430 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125438 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125444 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125467 has started for PR 28969 at commit |
|
Test build #125504 has finished for PR 28969 at commit
|
|
Test build #125519 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125541 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125560 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125575 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125607 has finished for PR 28969 at commit
|
|
Test build #125629 has finished for PR 28969 at commit
|
|
Test build #125652 has finished for PR 28969 at commit
|
|
retest this please |
|
Test build #125673 has finished for PR 28969 at commit
|
|
Merged to master. |
### What changes were proposed in this pull request? This PR aims to upgrade to ZStd 1.4.5-4. ### Why are the changes needed? ZStd 1.4.5-4 fixes the following. - luben/zstd-jni@3d16e51 - luben/zstd-jni@3d51bdc ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the Jenkins. Closes apache#28969 from williamhyun/zstd2. Authored-by: William Hyun <[email protected]> Signed-off-by: HyukjinKwon <[email protected]>
What changes were proposed in this pull request?
This PR aims to upgrade to ZStd 1.4.5-4.
Why are the changes needed?
ZStd 1.4.5-4 fixes the following.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the Jenkins.