MartijnVisser opened a new pull request, #27722:
URL: https://github.com/apache/flink/pull/27722
## What is the purpose of the change
CI test runs produce excessive DEBUG log output in the GitHub Actions
console. The primary source is Maven Shade Plugin bytecode rewriting messages
(`Keeping original class bytecode`, `Rewrote class bytecode`) that appear
during test runs. The shade DEBUG flag
(`-Dorg.slf4j.simpleLogger.log.org.apache.maven.plugins.shade=DEBUG`) was added
globally in FLINK-38711 for the license checker, but it only needs to be active
during the compile/deploy step. Additionally, `log4j.properties` enables DEBUG
for ZooKeeper `FinalRequestProcessor` and leader election/retrieval packages,
adding unnecessary noise to test log files.
## Brief change log
- Scope the shade plugin DEBUG logging flag from global Maven options to the
specific `compile.sh` deploy invocation where `ShadeParser`/`NoticeFileChecker`
needs it
- Change ZooKeeper `FinalRequestProcessor` logger from DEBUG to INFO
- Remove DEBUG-level logging for `org.apache.flink.runtime.leaderretrieval`
and `org.apache.flink.runtime.leaderelection`
## Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Full validation requires a CI run: the packaging/licensing job should pass
(ShadeParser still sees DEBUG output from `compile.sh`), and test job console
output should no longer contain shade plugin bytecode rewriting noise.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
