-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
com.hazelcast.internal.serialization.impl.compact.schema.CompactSchemaReplicationSlowTest [API-2218] [HZ-4566] #26245
Labels
constant-test-failure
Module: Serialization
Source: Internal
PR or issue was opened by an employee
Team: Client
Team: Core
to-client-jira
to-jira
Type: Test-Failure
Milestone
Comments
Internal Jira issue: API-2218 |
Internal Jira issue: HZ-4566 |
devOpsHazelcast
pushed a commit
that referenced
this issue
Mar 19, 2024
…t` [HZ-4566][API-2218] (#1133) [Several tests are failing](https://hazelcast.atlassian.net/browse/HZ-2245) only on Azul Prime JDKs due to an incompatibility between it and Mockito. Although in most cases we can replace a mocked concrete class with a mocked interface instead, here it's the `spy` functionality being used on real instances and there's no such workaround. To address this: - Refactored `CompactSchemaReplicationSlowTest` and `CompactSchemaReplicationTest` to move replicated logic into parent `CompactSchemaReplicationTestBase` - _Where possible_ replaced checking whether a method was called (via `spy`) to instead check the effect of that method - E.G. rather than checking `onSchemaAckRequest` is never called, instead check that the `replicationStatus` != `REPLICATED`, which is the effect of the method being called. - this cannot be done in every scenario (e.g. asserting that a method is called exactly 100 times when it has no side effect), and while it _would_ be possible to replicate the `spy` functionality with some invocation-counting delegate wrapper, as the tests pass this doesn't _appear_ to be necessary - Finally, understanding that checking a method is/isn't called is equivalent to checking the `replicationStatus`, identified some of the assertions were duplicated and redundant - now removed I *have* been able to [test this fix in a Jenkins job](https://hazelcast.atlassian.net/browse/HZ-4566?focusedCommentId=95093) to give some confidence it addresses the issue. Fixes: [HZ-4566](https://hazelcast.atlassian.net/browse/HZ-4566), [API-2218](https://hazelcast.atlassian.net/browse/API-2218), #26245 [HZ-4566]: https://hazelcast.atlassian.net/browse/HZ-4566?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ GitOrigin-RevId: 79092b41a4bc0c870f47a6fddd6cd73c41dc7682
Fails constantly on zing-17 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
constant-test-failure
Module: Serialization
Source: Internal
PR or issue was opened by an employee
Team: Client
Team: Core
to-client-jira
to-jira
Type: Test-Failure
master (commit 5ecb79121243fb5470750c592c41e63690a0b737)
Failed on zing-17: https://jenkins.hazelcast.com/job/Hazelcast-master-ZingJDK17-nightly/63/testReport/com.hazelcast.internal.serialization.impl.compact.schema/CompactSchemaReplicationSlowTest/
Following tests failed:
testSchemaReplication_whenAMemberThrowsRetryableExceptionAllTheTime_duringPreparationPhase
testSchemaReplication_whenAMemberThrowsRetryableExceptionAllTheTime_duringAcknowledgmentPhase
Stacktrace:
Standard output can be found here - https://s3.console.aws.amazon.com/s3/buckets/j-artifacts/Hazelcast-master-ZingJDK17-nightly/63/
The text was updated successfully, but these errors were encountered: