AVRO-3691:[maven build]Add nondex:2.1.1 to maven build section #2016
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 is the purpose of the change
Nondex is a tool that helps improve the reliability and security of Java applications by detecting and eliminating nondeterministic behavior. This is accomplished through a combination of static analysis, runtime instrumentation, and data collection.
One of the main advantages of using nondex is that it can help identify and fix issues that are difficult to reproduce and debug. It can also help prevent security vulnerabilities by identifying and eliminating potential exploits that rely on nondeterministic behavior.
The purpose of adding nondex to the maven build section is to allow developers to easily incorporate this tool into their build and testing process. This will help ensure that the application is as reliable and secure as possible, providing value to both developers and users.AVRO-3691
Run the
mvn nondex:nondexcommand can discover two flaky tests. These tests have now been fixed in PR AVRO-3690 and AVRO-3689.Run the command
mvn nondex:nondex -DnondexRuns=10, NonDex can found more flaky tests that were not detected by the initial run.Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Documentation