Fix non-deterministic tests for issue#3149 #3150
Merged
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 this PR does / why we need it
This PR addresses non-deterministic behavior in two specific tests, ensuring consistent and predictable results across builds.
Summary of Changes
Issue2959.java:
test()
to enforce a consistent ordering of fields in the expected output, matching it with the actual output format.DubboTest4.java:
test6()
to handle expected exceptions properly, accounting for specific exceptions (e.g.,java.io.IOException
) rather than returning null.Testing Instructions
The modifications can be validated using the NonDex plugin to simulate non-deterministic behavior:
Checklist