build: avoid bazel analysis cache discarding #17461
Merged
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
It looks like Bazel sometimes discards the analysis cache when switching between testing/running and plain building. This is because b3a0037 introduced a flag for disabling legacy bazel behavior. This flag has been only applied to "run" and "test", but not for "build". This means that we accidentally switch the environment, and Bazel discards the analysis cache (slowing down the development).
devversion
added
pr: merge safe
target: patch
googlebot
added
the
cla: yes
josephperrott
added
pr: lgtm
action: merge
|
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.
5 participants
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.
It looks like Bazel sometimes discards the analysis cache
when switching between testing/running and plain building.
This is because b3a0037 introduced a flag for disabling
legacy bazel behavior. This flag has been only applied to "run"
and "test", but not for "build". This means that we accidentally
switch the environment, and Bazel discards the analysis cache