-
Notifications
You must be signed in to change notification settings - Fork 3
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
Call echo_logs only when in DEBUG mode #167
Conversation
Codecov ReportBase: 86.72% // Head: 86.54% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #167 +/- ##
==========================================
- Coverage 86.72% 86.54% -0.18%
==========================================
Files 9 9
Lines 904 907 +3
==========================================
+ Hits 784 785 +1
- Misses 120 122 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
519c085
to
9dd8a9f
Compare
This reverts commit ff15465.
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.
This looks all good to me! Thanks!
I am going to release it after this one is merged. |
@unkcpz thanks. Feel free to merge, I do not have permissions. |
@danielhollas merged thanks!
Let me know if you need higher permission for convenient management. |
The
echo_logs
function prints out the logs from the container (i.e. the output ofaiidalab-launch logs
) while the user waits for the container to start. However, logs are printed withlogging.DEBUG
so there's no point in calling this function unless this level of logging is enabled (via the-vvv
cmdline parameter).We have some indication that this function is problematic in #154 so calling it only when neccessary might help. We also have issues with flaky tests, #163. While the change here does not solve the flakiness (see failures here and here), it does seem to help since the test suite no longer times out, but actually fails in a reasonable amount of time. I haven't been able to pinpoint the reason for the failures, looking at the error messages it seems that the container fails to start randomly. So more investigation is needed but this seems to be a step in right direction at least.