You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2026/03/04 08:34:00 UTC
[jira] [Resolved] (FLINK-39181) Reduce Verbose DEBUG Logging in CI
[ https://issues.apache.org/jira/browse/FLINK-39181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Visser resolved FLINK-39181.
------------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
Fixed in apache/flink@master 916faa8d82665433d5592d5ed20f9b784e1af9e4
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)