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

provider/google: Add an additional delay when checking for sql operations #15170

Merged
merged 1 commit into from
Jun 9, 2017

Conversation

danawillow
Copy link
Contributor

This should fix #13091, as well as some of our failing tests.

The failures are happening because for some reason, creating an operation and then immediately reading it back does not always succeed. This adds a bit of a delay between the create and read portions of the operation. We may need to fiddle with the numbers a bit in the future (this is hard to test since most of the time, things do work as expected), but it's at least a start.

@stack72
Copy link
Contributor

stack72 commented Jun 9, 2017

LGTM! Thanks for this @danawillow :)

@stack72 stack72 merged commit 93c6c0d into hashicorp:master Jun 9, 2017
@danawillow danawillow deleted the is-13091 branch June 9, 2017 16:58
@ghost
Copy link

ghost commented Apr 11, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Randomly fails to create google_sql_database_instance due to timing issue
2 participants