Which version of Kotest are you using
6.0.1

Actual result:
I noticed 6.x Gradle plugin became very noisy when applied to multi-module project. On every configuration phase it prints tons of Configuring kotest task logs ("number of targets" times "number of gradle modules with kotest plugin applied").

Looking at the source code this is because the usage of print calls

Expected result:
lifecycle task like information the test has been configured is moved to logger.info() or lower, not printed by defult on every run, to avoid obscuring build output