Fix unreliable behavior in Unit Test #9251
Merged
Conversation
This file contains 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
ScheduleSignHandlerTest `handleExecutesImmediateIfPossible` was not behaving deterministically. This was traced to a HashSet that was allowing duplicate PBJ values, somehow, for reference-equal objects. The set implementation was changed to LinkedHashSet, and appears to be behaving correctly now. Signed-off-by: Joseph Sinclair <joseph.sinclair@swirldslabs.com>
|
Kudos, SonarCloud Quality Gate passed!
|
mhess-swl
reviewed
Oct 13, 2023
...rc/test/java/com/hedera/node/app/service/schedule/impl/handlers/ScheduleSignHandlerTest.java
Show resolved
Hide resolved
mhess-swl
approved these changes
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ScheduleSignHandlerTest
handleExecutesImmediateIfPossiblewas not behaving deterministically. This was traced to a HashSet that was allowing duplicate PBJ values, somehow, for reference-equal objects. The set implementation was changed to LinkedHashSet, and appears to be behaving correctly now.