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

bug 1894925: change blocking timeout to 5 #6608

Merged
merged 1 commit into from
May 7, 2024
Merged

Conversation

willkg
Copy link
Collaborator

@willkg willkg commented May 7, 2024

This changes the blocking timeout to 5s for waitfor--previously it used the socket default timeout of 1s.

The theory is that in CI, it's taking longer than 1s for localstack to respond sometimes which causes CI to fail.

@willkg willkg requested a review from a team as a code owner May 7, 2024 18:15
This adds handling for TimeoutError so it'll go through the loop again.
It increases the blocking timeout to 2 which is slightly longer than 1s.
It also changes everything to f-strings.

The theory is that in CI, it's taking longer than 1s for localstack to
respond sometimes which causes CI to fail and because the loop didn't
handle TimeoutError, it would die immediately.
@willkg willkg force-pushed the willkg-bug-1894925-waitfor branch from 935ff40 to 34d197c Compare May 7, 2024 18:23
@willkg willkg merged commit b2ecba3 into main May 7, 2024
1 check passed
@willkg
Copy link
Collaborator Author

willkg commented May 7, 2024

Thank you!

This passed two CI attempts, so I think it probably helps. Maybe.

@willkg willkg deleted the willkg-bug-1894925-waitfor branch May 7, 2024 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants