When org.gradle.logging.level=warn, koverPrintCoverage does not produce any output.
Expected behavior
org.gradle.logging.level is used to control logging. Logging is a passive way to keep information on problems, errors, and just general information of a process. When org.gradle.logging.level=warn, we are saying that we only want warnings; we only want actionable information kept.
koverPrintCoverage is not passive logging. It is an optional task that is triggered manually when we want to see coverage information. It should not require that we set org.gradle.logging.level=lifecycle. Unlike all of the other information that is printed at the lifecycle log level, koverPrintCoverage is information that we have manually triggered to see.
Compare koverPrintCoverage with tasks. If org.gradle.logging.level=warn and we run ./gradlew tasks, we still see the printed output from the tasks task. koverPrintCoverage should work the same way.
Describe the bug
When
org.gradle.logging.level=warn
,koverPrintCoverage
does not produce any output.Expected behavior
org.gradle.logging.level
is used to control logging. Logging is a passive way to keep information on problems, errors, and just general information of a process. Whenorg.gradle.logging.level=warn
, we are saying that we only want warnings; we only want actionable information kept.koverPrintCoverage
is not passive logging. It is an optional task that is triggered manually when we want to see coverage information. It should not require that we setorg.gradle.logging.level=lifecycle
. Unlike all of the other information that is printed at thelifecycle
log level,koverPrintCoverage
is information that we have manually triggered to see.Compare
koverPrintCoverage
withtasks
. Iforg.gradle.logging.level=warn
and we run./gradlew tasks
, we still see the printed output from thetasks
task.koverPrintCoverage
should work the same way.