fix(sql/testing): use wait.ForSQL when readying cockroach #1183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've noticed connections on cockroachdb attempting to apply migrations are getting stuck a lot during testing.
I'm unsure if this will help. However, I decided to attempt and migrate to the
wait.ForSQL
pattern for cockroach.Just in case there is some kind of race when cockroach HTTP server is ready but SQL is in a bad state.
Example: https://github.com/flipt-io/flipt/actions/runs/3578054959/jobs/6017766294