You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2026/03/01 11:33:00 UTC

[jira] [Created] (FLINK-39181) Reduce Verbose DEBUG Logging in CI

Martijn Visser created FLINK-39181:
--------------------------------------

             Summary: Reduce Verbose DEBUG Logging in CI
                 Key: FLINK-39181
                 URL: https://issues.apache.org/jira/browse/FLINK-39181
             Project: Flink
          Issue Type: Improvement
          Components: Build System / CI
            Reporter: Martijn Visser
            Assignee: Martijn Visser


CI test runs produce excessive [DEBUG] log output in the console. The primary noise comes from Maven Shade Plugin bytecode rewriting messages like:
 [DEBUG] Keeping original class bytecode: org/apache/flink/table/planner/...
 [DEBUG] Rewrote class bytecode: org/apache/flink/table/planner/...

 These are caused by -Dorg.slf4j.simpleLogger.log.org.apache.maven.plugins.shade=DEBUG set globally in tools/ci/maven-utils.sh (line 76). This flag was intentionally added (FLINK-38711) because shade plugin 3.6.1 changed "Including X in the shaded jar" messages from INFO to DEBUG, and the ShadeParser / NoticeFileChecker (license check) parses those lines. However, the flag is set globally and affects all CI Maven invocations, including test runs where it's not needed.

Additionally, tools/ci/log4j.properties enables DEBUG for leader election and ZooKeeper packages, adding noise to test log files.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)