-
Notifications
You must be signed in to change notification settings - Fork 4
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
[WIP]: HEALTHCHECK-based container readiness test #80
base: develop
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #80 +/- ##
===========================================
- Coverage 100% 99.69% -0.31%
===========================================
Files 26 29 +3
Lines 2565 2612 +47
Branches 162 167 +5
===========================================
+ Hits 2565 2604 +39
- Misses 0 4 +4
- Partials 0 4 +4
Continue to review full report at Codecov.
|
# Close the stream's underlying response object (if it has one) to | ||
# avoid potential socket leaks. | ||
if hasattr(stream, '_response'): | ||
stream._response.close() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we close the stream here?
except TimeoutError: | ||
raise TimeoutError( | ||
"Timed out waiting for 'health_status' event with status '{}'" | ||
.format(status)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should pass the timeout message to stream_timeout
instead of catching and throwing? That would reduce boilerplate, but also add the timeout machinery to the stack trace.
No description provided.