github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

some logging level got changed between 0.10/0.11 (9 is lowest log level to capture messages in LogCaptureTestCase now)

pull/2601/head
sebres 2020-01-08 21:43:27 +01:00
parent 587e4ff573
commit ac41b8f3be
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
fail2ban/server/action.py
View File

@ -1008,7 +1008,7 @@ class CommandAction(ActionBase):
RuntimeError
If command execution times out.
"""
if logSys.getEffectiveLevel() < logging.DEBUG: # pragma: no cover
if logSys.getEffectiveLevel() < logging.DEBUG:
logSys.log(9, realCmd)
if not realCmd:
logSys.debug("Nothing to do")

7
fail2ban/tests/utils.py
View File

@ -754,10 +754,11 @@ class LogCaptureTestCase(unittest.TestCase):
# Let's log everything into a string
self._log = LogCaptureTestCase._MemHandler(unittest.F2B.log_lazy)
logSys.handlers = [self._log]
if self._old_level <= logging.DEBUG:
# lowest log level to capture messages (expected in tests) is Lev.9
if self._old_level <= logging.DEBUG: # pragma: no cover
logSys.handlers += self._old_handlers
else: # lowest log level to capture messages
logSys.setLevel(logging.DEBUG)
if self._old_level > logging.DEBUG-1:
logSys.setLevel(logging.DEBUG-1)
super(LogCaptureTestCase, self).setUp()
def tearDown(self):