Closed rickemery closed 6 years ago
This is on dhscratch
and dev
branches
breadcrumb for whomever fixes this: Run py.test
with a debug statement right before log_level
getting set, see if it's already there.
It looks like log_level
is set by new versions of pytest, as pytest has integrated logging that it didn't have previously:
https://docs.pytest.org/en/latest/logging.html
However, log_level
itself is undocumented (naturally).
It looks like pytest 3.2.5 is safe from this problem, and this other one I found while trying to fix it:
https://github.com/pytest-dev/pytest/issues/3046
To fix this issue itself, I want to remove logging from the gips system tests completely. It was a misfeature that I kinda regret: All people ever did was pass -s --ll debug
, as a practically mandatory feature for gips system test runs.
What you're supposed to do instead is just print
things, then rely on pytest's -s
option to control whether or not you see your printouts. That's what I want to put in its place.
Work around: Delete
parser.addoption("--log-level", dest='log_level', help=help_str)
fromconftest.py