Disable //test/config_test:config_test under coverage#45843
Merged
Conversation
Signed-off-by: Yan Avlasov <yan_avlasov@hotmail.com>
yanavlasov
requested review from
RyanTheOptimist,
abeyad,
mattklein123 and
tyxia
as code owners
RyanTheOptimist
approved these changes
Jun 30, 2026
RyanTheOptimist
left a comment
RyanTheOptimist
left a comment
Contributor
There was a problem hiding this comment.
LGTM, but can you include the motivation in the PR description.
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
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.
This test links all extensions and verifies that example configs are valid. The binary is very large with coverage instrumentation and will soon fail to link due to 36Gb limit on the link artifacts in remote bazel.
The value of the test is very low as the config parsing coverage should be attained via unit or integration tests. Disabling this binary will save build resources without negative impact on useful coverage.
Risk Level: low
Testing: unit tests
Docs Changes: no
Release Notes: no
Platform Specific Features: no