Skip to content

Conversation

olavloite
Copy link
Collaborator

The ITClosedSessionTest could cause a flaky failure because it deletes sessions on the server and then repeatedly executes queries on the session until it returns a NOT_FOUND error. The actual deletion could however happen exactly at the moment that the test query was executed, which will cause Cloud Spanner to return a different error message than the standard 'Session not found' error message.

Fixes #41

The ITClosedSessionTest could cause a flaky failure because it
deletes sessions on the server and then repeatedly executes queries
on the session until it returns a NOT_FOUND error. The actual deletion
could however happen exactly at the moment that the test query was
executed, which will cause Cloud Spanner to return a different error
message than the standard 'Session not found' error message.

Fixes #41
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jan 23, 2020
Copy link
Contributor

@mbril mbril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ITClosedSessionTest.testReadWriteTransactionNoRecreation is flaky
3 participants