Fix Flaky Test CommonExceptionDataTest#should_include_code_in_json_when_code_is_not_null
#4992
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.
Issue
Test
CommonExceptionDataTest#should_include_code_in_json_when_code_is_not_nullis flaky. See #4991Fix
This fix decodes the JSON and asserts the key–value pairs on a map, so the test checks semantic content instead of exact string formatting or key order. It keeps the original goal of verifying that both "code" and "message" fields have the correct values, while removing flakiness caused by unpredictable key ordering during JSON serialization.
Checklist
[SCB-XXX] Fixes bug in ApproximateQuantiles, where you replaceSCB-XXXwith the appropriate JIRA issue.mvn clean install -Pitto make sure basic checks pass. A more thorough check will be performed on your pull request automatically.