-
Notifications
You must be signed in to change notification settings - Fork 39
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
Tests are failing with napari 0.5.0 #443
Comments
Based on my investigations I think this is related to the logging level set, if "DEBUG" is set then these errors crop up while if everything is "INFO" and below it seems to work fine. Upon further investigation this seems to only matter for logging to file and not to console. This was the minimal example I've been working with:
From what I understand it has something to do with the use of |
I've got a better minimal example now that doesn't use
|
Thanks @IgorTatarnikov, yes I'd say it's worth raising an issue, or asking on Zulip. My only confusion though - I don't think the cellfinder plugin (unlike brainreg) logs to file? |
The cellfinder plugin doesn't directly, there's only one time logging is invoked during our test suite:
Which calls: cellfinder/cellfinder/core/train/train_yml.py Lines 265 to 274 in 71d17ee
Commenting out that one line fixes the errors. |
So the logger from a non-napari-related test function persists across tests??? 😱 TIL! |
Just noting that following #444 we should make sure to update the tests (removing the |
@alessandrofelder's hypothesis - "napari fixtures are now cleverer and fail your tests if you don't clean up your widgets properly"
We should look into this and get the tests passing again (e.g. by making sure all qt widgets have parents)
The text was updated successfully, but these errors were encountered: