Fix gazelle warning when fuzzing_enabled is not provided
#7260
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
farazdagi
added
Ready For Review
Codecov Report
@@ Coverage Diff @@
## master #7260 +/- ##
==========================================
- Coverage 61.83% 61.57% -0.27%
==========================================
Files 417 417
Lines 33270 33109 -161
==========================================
- Hits 20574 20386 -188
- Misses 9763 9795 +32
+ Partials 2933 2928 -5 |
nisdas
approved these changes
Sep 17, 2020
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.
What type of PR is this?
What does this PR do? Why is it needed?
bazel run //:gazelle, I see the following gazelle warning:fuzzing_enabledflag is not set,bazel run //:gazelledoesn't emit any warnings.Which issues(s) does this PR fix?
N/A
Other notes for review