This repository was archived by the owner on Oct 24, 2025. It is now read-only.
fix flaky test in JSONRegionAdviceIntegrationTests#132
Open
CharlesZKQ wants to merge 1 commit intospring-attic:mainfrom
Open
fix flaky test in JSONRegionAdviceIntegrationTests#132CharlesZKQ wants to merge 1 commit intospring-attic:mainfrom
CharlesZKQ wants to merge 1 commit intospring-attic:mainfrom
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
In
org.springframework.data.gemfire.serialization.json.JSONRegionAdviceIntegrationTests, the testsobjectToJSon(),templateFind(),templateFindUnique(),templateQuery()are all flaky due to the non-deterministic property ofgetDeclatedFields()(please refer document), which is used in serialization oforg.apache.geode.cache.Regionandcom.fasterxml.jackson.databind.ObjectMapper.writeValueAsString(). I fixed it by adding @JsonPropertyOrder annotation to fix fix its order of properties during serialization of putting into Region, and addingMapperFeature.SORT_PROPERTIES_ALPHABETICALLYto make the mapper in alphabetical order.