Fix: Stabilize JsonUtilsTest.consistentTest to prevent Non-Dex nondeterminism
#15746
+8
−6
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?
This PR stabilizes
JsonUtilsTest.consistentTest, which previously exhibited nondeterministic failures under random execution ordersRoot Cause
The issue stemmed from comparing raw JSON strings produced by different JSON frameworks (
fastjson2,fastjson,gson,jackson). These frameworks may serialize map fields in different key orders, leading to order-dependent failures.Changes Made
Updated assertions to compare JSON structures instead of raw strings using:
This ensures comparisons are semantically equivalent and order-insensitive.
Added
throws Exceptionto the test method to handle Jackson’s checked exceptions.Verification
You can try running the following snippet of code from the dubbo repo root, on both pre-fix and post-fix code
The test should fail intermittently on the pre-fix version, but pass consistently across all seeds on the post-fix version.
NonDex run logs will be available under the
dubbo-common/.nondexdirectory.Checklist