Configuration property %test,prod.quarkus.log.category."...".level is ignored in native mode

[yrodiere]

Describe the bug

Follows up on #37177 (comment) ; it would seem quarkus.test.integration-test-profile has nothing to do with the problem: it's just that log levels are ignored in native mode when set through a configuration property that mentions multiple configuration profiles.

Expected behavior

I would expect all of these to be taken into account:

• %prod.hello.message=...
• %test.quarkus.log.category."...".level=TRACE
• %prod.quarkus.log.category."...".level=TRACE
• %test,prod.quarkus.log.category."...".level=TRACE

Actual behavior

These work fine:

• %prod.hello.message=...
• %test.quarkus.log.category."...".level=TRACE
• %prod.quarkus.log.category."...".level=TRACE

This works fine in surefire (JVM) tests:

• %test,prod.quarkus.log.category."...".level=TRACE

... but is ignored in failsafe (native) tests and when running the native executable.

How to Reproduce?

git clone -b log-level-ignored https://github.com/yrodiere/quarkus-playground.git

See https://github.com/yrodiere/quarkus-playground/tree/log-level-ignored, in particular the README for details.

Output of uname -a or ver

Linux yrodiere-thinkpadp1gen4i.remote.csb 6.6.3-100.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Nov 28 20:36:17 UTC 2023 x86_64 GNU/Linux

Output of java -version

openjdk version "17.0.7" 2023-04-18 OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7) OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode, sharing)

Quarkus version or git rev

3.6.0

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39) Maven home: /home/yrodiere/.m2/wrapper/dists/apache-maven-3.8.8-bin/67c30f74/apache-maven-3.8.8 Java version: 17.0.7, vendor: Eclipse Adoptium, runtime: /home/yrodiere/tools/java/jdk-17.0.7+7 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "6.6.3-100.fc38.x86_64", arch: "amd64", family: "unix"

Additional information

No response

[quarkus-bot]

/cc @zakkak (native-image)

[yrodiere]

Hey @radcortez ; see above. I think there might be something specific in the logging configuration in native mode that leads to multi-profile configuration properties being ignored.

[radcortez]

I'll have a look.