[
https://issues.apache.org/jira/browse/IMPALA-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-10304.
------------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Pytest logging is not using the expected INFO log level
> -------------------------------------------------------
>
> Key: IMPALA-10304
> URL: https://issues.apache.org/jira/browse/IMPALA-10304
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 4.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 4.0
>
>
> In IMPALA-10302, we noticed that query_test/test_scanners_fuzz.py was not
> logging the INFO statements that are useful for debugging. Testing indicated
> that it would only log WARNING or above. There was a specific fix for that
> test, but this indicates a broader issue for any other tests that do logging
> at the INFO level.
> We have this code in our tests/conftest.py:
> {noformat}
> def configure_logging():
> # Use a "--" since most of our tests output SQL commands, and it's nice to
> # be able to copy-paste directly from the test output back into a shell to
> # try to reproduce a failure.
> logging.basicConfig(level=logging.INFO, format=LOG_FORMAT){noformat}
> This is setting the logging level to INFO and using a specific log format, so
> it is unexpected that we are only logging at WARNING and above. We need to
> figure out what changed and why it isn't respecting the logging level from
> conftest.py. This impacts our ability to debug test failures.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
