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

ScheduledRetryingExecutorTest.testCancelGetAttempt is flaky #2851

Open
blakeli0 opened this issue Jun 4, 2024 · 0 comments
Open

ScheduledRetryingExecutorTest.testCancelGetAttempt is flaky #2851

blakeli0 opened this issue Jun 4, 2024 · 0 comments
Assignees
@blakeli0
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@blakeli0
Copy link
Collaborator

blakeli0 commented Jun 4, 2024

ScheduledRetryingExecutorTest.testCancelGetAttempt failed in the nightly tests.

Error:  com.google.api.gax.retrying.ScheduledRetryingExecutorTest.testCancelGetAttempt(boolean)[2] -- Time elapsed: 0.013 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: not <null>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
	at org.junit.jupiter.api.AssertNotNull.failNull(AssertNotNull.java:49)
	at org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:35)
	at org.junit.jupiter.api.AssertNotNull.assertNotNull(AssertNotNull.java:30)
	at org.junit.jupiter.api.Assertions.assertNotNull(Assertions.java:304)
	at com.google.api.gax.retrying.ScheduledRetryingExecutorTest.testCancelGetAttempt(ScheduledRetryingExecutorTest.java:244)

See https://github.com/googleapis/sdk-platform-java/actions/runs/9278818408/job/25530390444 for details.
@blakeli0 blakeli0 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 4, 2024
@blakeli0 blakeli0 mentioned this issue Jun 4, 2024
Closed
@mpeddada1 mpeddada1 mentioned this issue Jul 19, 2024
Closed
@blakeli0 blakeli0 self-assigned this Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@blakeli0 blakeli0

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blakeli0