Fixed flaky test in DiscoveryFactoryTest.java #1194
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.
Fixed flaky tests with error msg related to
org.mockito.exceptions.verification.TooManyActualInvocations
that caused byverify(runtimeContext).isDisablePeerDiscovery();
in classcom.quorum.tessera.discovery.DiscoveryFactoryTest
.Error msg:
Root cause:
It because this class doesn't reset the mocked objects at the very beginning, though we did reset
MockContextHolder
after each test. If we called this class right after other classes that have mocked objects unrested, there will be flaky tests.The
org.mockito.exceptions.verification.TooManyActualInvocations
is found by running iDFlakies. After fixing the issue, there's no flaky tests inDiscoveryFactoryTest.java