build: disable runfile creation in bazel_build job #16824
Closed
Conversation
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
Disables runfile tree creation in the `bazel_build` job. The runfile trees are only needed for execution of test/binary targets, but this is not the case for the `bazel_build` job. Runfile trees are not cached and therefore cause the job to not fully leverage remote caching.
googlebot
added
the
cla: yes
|
Moving that into #16823 if possible. Looks like a few targets that aren't executed on |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Disables runfile tree creation in the
bazel_buildjob. The runfile treesare only needed for execution of test/binary targets, but this is not the
case for the
bazel_buildjob. Runfile trees are not cached and thereforecause the job to not fully leverage remote caching.
For testing jobs we still get the overhead of creating runfile tree's even if
the test results were part of the remote cache. Seems like a bug/issue that
is tracked on the bazel side: bazelbuild/bazel#6627