Logging tests not using default config values? #1284
Merged
+35
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the process of testing the 0.2.4 release I experienced two test failures on my own system when running
astropy.test()in a Python session. Both failures were in the logging module and looked something like this:I realized that this was just occurring because in my
~/.astropy/config/astropy.cfgI set the log level toDEBUG, whereas the default should beINFO. I thought we had fixed the tests to always use the default config settings... Or am I mistaken on that? (Note: I do see potential value in being able to run the tests with different local config values, but if that's a desirable thing to do the tests need to be designed to support different configurations where applicable).