Increased timeout to avoid service unavailable error #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chayim
reviewed
Jan 30, 2024
| @@ -6,7 +6,7 @@ fi | |||
|
|
|||
| ## Build infrastructure ## | |||
| docker-compose up -d | |||
| sleep 10 | |||
| sleep 15 | |||
There was a problem hiding this comment.
How about instead, we use health checks? Yes, we still need timeouts due to time to settle?
There was a problem hiding this comment.
Good point, I'm searching for an alternative for this hacks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Timeout should be increased cause 10 seconds is not enough for GitHub actions CI to properly run infrastructure after
docker-compose up -d. It leads to this kind of error when it's tries to create cluster, but service still unavailablehttps://github.com/vladvildanov/predis/actions/runs/7709095086/job/21009537690