Conversation

olavloite

As noted in #2748, the Spanner samples should use the libraries-bom:5.2.0 to import dependencies.

@olavloiteolavloite requested a review from a team April 24, 2020 12:24
@googlebotgooglebot added the cla: yesThis human has signed the Contributor License Agreement.label Apr 24, 2020
@olavloite

The build failure is caused by googleapis/java-spanner#179

@lesv

So we need to wait for the next spanner update?

@olavloiteolavloite added the kokoro:force-runAdd this label to force Kokoro to re-run the tests.label Apr 24, 2020
@kokoro-teamkokoro-team removed the kokoro:force-runAdd this label to force Kokoro to re-run the tests.label Apr 24, 2020
@olavloite

So we need to wait for the next spanner update?

Not necessarily. This is a flaky test failure that is not really related to the samples.

This failure occurs in the case that:

  1. A non-idempotent admin RPC, such as CreateDatabase or CreateBackup, fails with an error that would normally be retryable, such as UNAVAILABLE.
  2. The Spanner client library will in the above case query the backend for any corresponding long-running operation to check whether the RPC was successfully executed or not. If the operation is found, the Spanner client will start tracking the progress of that operation. If it is not found, a new RPC will be executed.

The query in step 2 above has a problem that the query can be specified in the wrong order, and will in that case be rejected by the backend. But for that to happen, the random error in step 1 needs to happen first. I'll start the build again and see if the error happens again.

@olavloiteolavloite merged commit 40df395 into GoogleCloudPlatform:master Apr 24, 2020
@olavloiteolavloite deleted the spanner-use-libraries-bom branch April 24, 2020 18:39
Sign up for free to join this conversation on . Already have an account? Sign in to comment
cla: yesThis human has signed the Contributor License Agreement.
None yet

Successfully merging this pull request may close these issues.