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.

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

ReadAsyncTest.readOnlyTransaction is flaky #3481

Closed
olavloite opened this issue Nov 19, 2024 · 1 comment · Fixed by #3550
Closed

ReadAsyncTest.readOnlyTransaction is flaky #3481

olavloite opened this issue Nov 19, 2024 · 1 comment · Fixed by #3550
Assignees
Labels
api: spanner Issues related to the googleapis/java-spanner API. type: process A process-related concern. May include testing, release, or the like.

Comments

@olavloite
Copy link
Collaborator

Error:  Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.152 s <<< FAILURE! -- in com.google.cloud.spanner.ReadAsyncTest
Error:  com.google.cloud.spanner.ReadAsyncTest.readOnlyTransaction -- Time elapsed: 0.051 s <<< FAILURE!
unexpected (1): v10
---
expected      : [v1, v2, v3, v10, v11, v12]
but was       : [v1, v2, v3, v10, v10, v11, v12]
	at com.google.cloud.spanner.ReadAsyncTest.readOnlyTransaction(ReadAsyncTest.java:326)
@olavloite olavloite added the type: process A process-related concern. May include testing, release, or the like. label Nov 19, 2024
@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/java-spanner API. label Nov 19, 2024
@olavloite
Copy link
Collaborator Author

Another flake:

Error:  Failures: 
Error:    ReadAsyncTest.readOnlyTransaction:326 unexpected (1): v10
---
expected      : [v1, v2, v3, v10, v11, v12]
but was       : [v1, v2, v3, v10, v10, v11, v12]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the googleapis/java-spanner API. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants