-
Notifications
You must be signed in to change notification settings - Fork 915
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
Enable ccache for cudfjni build in Docker #10790
Conversation
…d-in-docker-for-native
Signed-off-by: Gera Shegalov <[email protected]>
Signed-off-by: Gera Shegalov <[email protected]>
Co-authored-by: Jason Lowe <[email protected]>
- and fix bug of CUDF_CPP_BUILD_DIR parameter being ignored Signed-off-by: Gera Shegalov <[email protected]>
…d-in-docker-for-native
Signed-off-by: Gera Shegalov <[email protected]>
Signed-off-by: Gera Shegalov <[email protected]>
Codecov Report
@@ Coverage Diff @@
## branch-22.06 #10790 +/- ##
================================================
+ Coverage 86.40% 86.45% +0.04%
================================================
Files 143 143
Lines 22448 22491 +43
================================================
+ Hits 19396 19444 +48
+ Misses 3052 3047 -5
Continue to review full report at Codecov.
|
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.
Looks good, just a minor question about potentially simplifying a build line which is not crucial.
Co-authored-by: Jason Lowe <[email protected]>
@gpucibot merge |
This PR enables ccache support for
./build.sh clean cudfjar
.ccache 4.6 is built during image creation because ccacheversion available via
yum install
does not cache nvcc-compiled binaries.It's enabled by default for build.sh and repeated no-change build
PARALLEL_LEVEL=6 SKIP_TESTS=true time ./build.sh clean cudfjar
succeeds in 1.5 min on my machine. To disable set CCACHE_DISABLE=1 in the environment
It's not enabled for ./java/ci/build-in-docker.sh
Signed-off-by: Gera Shegalov [email protected]