Implement native analysis_test call.#15940
Merged
ShreeM01 merged 1 commit intobazelbuild:release-5.3.0from Jul 21, 2022
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The call defines a rule and a target on the BUILD thread. Since target names need to be unique so is the rule class name.
This removes boilerplate in analysis testing. This mechanism replaces rule.name mechanism, which will be removed.
If this becomes the default for analysis tests, rule call may be further simplified.
The implementation is safeguarded by experimental flag.
PiperOrigin-RevId: 462309501
Change-Id: I918ddcc8efd3b27f822998bcaa454e467a98b7ea