Repository navigation
What is general guidance around analysis cache thrashing when invoking bazel build --> bazel coverage --> bazel build? #22655
Unanswered
Ryang20718
asked this question in
Q&A
Replies: 1 comment 3 replies
|
We add those flags to |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
--collect_code_coverage and --instrumentation_filtercauses the analysis cache to thrash in CI when running bazel build --> bazel coverageWhat do most people do currently to avoid this?
separate output_base?
All reactions