-
Notifications
You must be signed in to change notification settings - Fork 104
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
Use ccache for CI #977
Open
davidbeckingsale
wants to merge
11
commits into
develop
Choose a base branch
from
feature/ccache
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Use ccache for CI #977
Changes from 4 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
dd92d4d
Update BLT to support ccache
davidbeckingsale c4cc486
Enable ccache for toss3 builds
davidbeckingsale f9d82de
Merge branch 'develop' into feature/ccache
rhornung67 47261a1
Merge branch 'develop' into feature/ccache
rhornung67 349df88
Merge branch 'develop' into feature/ccache
rhornung67 7ed4780
Merge branch 'develop' into feature/ccache
rhornung67 9923267
Merge branch 'develop' into feature/ccache
rhornung67 b7653ee
Merge branch 'develop' into feature/ccache
rhornung67 eaf03bd
Merge branch 'develop' into feature/ccache
rhornung67 7ad9c15
Merge branch 'develop' into feature/ccache
rhornung67 38a1847
Merge branch 'develop' into feature/ccache
rhornung67 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Submodule blt
updated
17 files
+50 −0 | .gitlab-ci.yml | |
+24 −0 | .gitlab/build_and_test.sh | |
+52 −0 | .gitlab/build_lassen.yml | |
+63 −0 | .gitlab/build_quartz.yml | |
+8 −0 | .mailmap | |
+8 −7 | RELEASE-NOTES.md | |
+1 −0 | cmake/BLTOptions.cmake | |
+68 −5 | cmake/BLTPrivateMacros.cmake | |
+11 −0 | cmake/SetupCompilerOptions.cmake | |
+26 −0 | docs/tutorial/unit_testing.rst | |
+2 −2 | host-configs/llnl/toss_3_x86_64_ib/[email protected] | |
+3 −3 | host-configs/llnl/toss_3_x86_64_ib/[email protected] | |
+62 −0 | tests/ctest-to-junit.xsl | |
+9 −0 | tests/internal/CMakeLists.txt | |
+28 −0 | tests/internal/src/hip_defines_test/CMakeLists.txt | |
+13 −0 | tests/internal/src/hip_defines_test/bar.cpp | |
+13 −0 | tests/internal/src/hip_defines_test/foo.cpp |
This file contains 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
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.
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.
Does ccache work well with a single location that may be targeted by several builds simultaneously? (Maybe it creates a unique subdir per configuration hash?)
Also, in the log I see:
Are we sure this is taken into account by BLT?
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.
Oops, that's the binary location, not the location of the data...
Then, where is the data stored? If it's in the working directory, then I'm afraid this won't help much. That's because the working directory changes with the runner hash, the job rank on the runner (0 to 7), and then we have no guarantee that the same target will be rebuilt there.
This is not a lost cause though.
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.
That's a typo in my BLT changes :D and we can change the location via a config file. I am trying to work out the best way to set up the config, I think we will need to it via env var.