-
Notifications
You must be signed in to change notification settings - Fork 270
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
logging in updater tests is weirdly broken #1083
Comments
After shutting the laptop down I realized we are probably not initializing logging when running the test "by hand", and then something does it during the test. We should do something like |
After spending a surprisingly long time on this log, I think I have found, if not a solution, at least an explanation.
|
I opened #1092 to start a discussion of the above in a way. |
Closing. update_tests.py output is still four screens of various ResourceWarnings but the output is not obviously broken anymore: Thanks! |
Something weird goes on in the updater tests logging. In the middle of the test (seemingly around the time the last root.json download fails during Updater.refresh()) logger level seems to somehow change to debug. It's not just that though: even if I change the level of some earlier logger calls (like changing logger.debug() to logger.error()) so that they become visible, they don't look the same as similar logging later on. The earlier output from e.g. logger.error() isn't prefixed with logger level and component.
Current behavior:
The text was updated successfully, but these errors were encountered: