Fix 3 Bazel related things which will make local development smoother #411
Conversation
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
This is more consistent, notably when directly running `bazelisk test //...` via the CLI instead of that script.
vorburger
force-pushed
the
fix-bazel-rebuild
branch
from
ff3ea81 to
6e1eff8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixed Bazel related things which will make local development smoother:
Fix pretty bad constant "discarding analysis cache" local build problem
Move
--nobuild_tests_onlyfromtest.bashinto.bazelrc: This is more consistent, notably when directly runningbazelisk test //...via the CLI instead of that script.Avoid calling Bazel twice for test and build: Inspired by How to build all buildable targets and test all testable targets bazelbuild/bazel#4257.