I think it's the latter. Let me try to add you to ...

# kotlintest

[LeoColman]

I think it's the latter. Let me try to add you to our conversation

[dave08]

Ok, it looks like the logback.xml configs were the problem:

<configuration>
    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
        <encoder>
            <pattern>%d{YYYY-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
        </encoder>
    </appender>
    <root level="trace">
        <appender-ref ref="STDOUT"/>
    </root>
    <logger name="org.eclipse.jetty" level="INFO"/>
    <logger name="io.netty" level="INFO"/>
    <logger name="i.m" level="INFO"/>
    <logger name="io.mockk" level="INFO"/>
</configuration>

Changing root to info now gives nice and clean logs again... I wonder if that's the Ktor default 🤔... I don't recall adding this. But it could be that a note in the docs won't hurt to know specific loggers being used in Junit5 and KotlinTest, so that setting the global level won't suddenly flood test runs with unecessary logs...