You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the example the first call to from_cmdline runs as expected logging messages to foo.log. However the second run (when no logcfg is provided also logs to the same file (appending log messages) and runs at the same level as configured in the first run.
The text was updated successfully, but these errors were encountered:
There are a few tests in jwst that use
logcfg
:https://github.com/spacetelescope/jwst/blob/8efc26fdbda7936199d1a05cb57707d2c1cb0665/jwst/pipeline/tests/test_calwebb_image2.py#L82-L84
https://github.com/spacetelescope/jwst/blob/8efc26fdbda7936199d1a05cb57707d2c1cb0665/jwst/pipeline/tests/test_calwebb_image2.py#L82C5-L82C11
These change global logging state and can lead to later tests that check log output failing. Here's a somewhat minimal example:
Running the example the first call to
from_cmdline
runs as expected logging messages tofoo.log
. However the second run (when nologcfg
is provided also logs to the same file (appending log messages) and runs at the same level as configured in the first run.The text was updated successfully, but these errors were encountered: