build: enable ClassInitializationDeadlock, SuppressWarnings the problems #15322
Conversation
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
Enable error-prone's ClassInitializationDeadlock check, which can statically detect bugs such as apache#15317 All problems were just suppressed with a 'FIXME' message, this check will at least prevent any new ones from showing up. There aren't that many problems, it just happens that some are caused by generated code, so you get a violation for each bit-per-value.
|
This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop receiving this reminder on future updates to the PR. |
dweiss
approved these changes
Oct 10, 2025
|
Awesome! Thanks @rmuir |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Enable error-prone's ClassInitializationDeadlock check, which can statically detect bugs such as #15317
All problems were just suppressed with a 'FIXME' message, this check will at least prevent any new ones from showing up.
There aren't that many problems, it just happens that some are caused by generated code, so you get a violation for each bit-per-value.