Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Investigate Flaky Tests in SequencerServerTest suite #3487

Closed
zfrenette opened this issue Jan 16, 2023 · 3 comments
Closed

Investigate Flaky Tests in SequencerServerTest suite #3487

zfrenette opened this issue Jan 16, 2023 · 3 comments
Assignees
@zfrenette
Labels
Test Failure Tests intermittently failing (test itself or source code)

Comments

@zfrenette
Copy link
Collaborator

Overview

Failure here: https://github.com/CorfuDB/CorfuDB/actions/runs/3926753423/jobs/6712761921.
Looks like a race in the suite.
@zfrenette zfrenette self-assigned this Jan 16, 2023
@zfrenette
Copy link
Collaborator Author

Looks like a similar type of issue to #3460

@zfrenette zfrenette mentioned this issue Jan 18, 2023
Merged
4 tasks
@zfrenette
Copy link
Collaborator Author

One such failure:

Error:  Tests run: 12, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.868 s <<< FAILURE! - in org.corfudb.infrastructure.SequencerServerTest
Error:  org.corfudb.infrastructure.SequencerServerTest.testSequencerTrimRequest  Time elapsed: 0.226 s  <<< ERROR!
org.mockito.exceptions.misusing.WrongTypeOfReturnValue: 

Long cannot be returned by getCurrentLayout()
getCurrentLayout() should return Layout
***
If you're unsure why you're getting above error read on.
Due to the nature of the syntax above problem might occur because:
1. This exception *might* occur in wrongly written multi-threaded tests.
   Please refer to Mockito FAQ on limitations of concurrency testing.

Since the health report scheduler is executing code on a separate thread, it can interfere with the specified mocked behaviour of relevant objects during the tests.

@zfrenette zfrenette added the Test Failure Tests intermittently failing (test itself or source code) label Jan 18, 2023
@zfrenette
Copy link
Collaborator Author

Resolving since #3492 is now merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zfrenette zfrenette

Labels
Test Failure Tests intermittently failing (test itself or source code)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zfrenette