quarkus.test.native-image-profile seems to be not reflected with Quarkus main

[rsvoboda]

Describe the bug

quarkus.test.native-image-profile seems to be not reflected with Quarkus main

security-openid-connect-client-quickstart is failing and it uses this property in https://github.com/quarkusio/quarkus-quickstarts/blob/main/security-openid-connect-client-quickstart/src/main/resources/application.properties#L14 to control port number

security-openid-connect-client-quickstart works well with Quarkus 3.17.4

When native binary is executed in the test INFO [io.quarkus] (main) Profile prod activated. appears in the log

WARN [io.qua.run.con.ConfigRecorder] (main) The profile 'prod' used to build the native image is different from the runtime profile 'test'. This may lead to unexpected results. is the thing that should appear in the log as quarkus.test.native-image-profile=test is set in the application properties

Expected behavior

security-openid-connect-client-quickstart passes with Quarkus main

Actual behavior

security-openid-connect-client-quickstart fails with Quarkus main, prod mode is used in execution and quarkus.test.native-image-profile=test is not reflected

How to Reproduce?

Make sure GraalVM or Mandrel is available, e.g. using sdk use java 23.1.5.r21-mandrel
Run

git clone https://github.com/quarkusio/quarkus-quickstarts -b development
cd quarkus-quickstarts/security-openid-connect-client-quickstart
#FAIL
mvn clean verify -Dnative -Dquarkus.platform.version=999-SNAPSHOT
#PASS
mvn clean verify -Dnative -Dquarkus.platform.version=3.17.4

Output of uname -a or ver

macOS

Output of java -version

Java 21

Quarkus version or git rev

Quarkus main fc237a6

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

No response

Additional information

No response

[quarkus-bot]

/cc @Karm (mandrel), @galderz (mandrel), @zakkak (mandrel,native-image)

[rsvoboda]

CC @sberyozkin

[sberyozkin]

Hi @rsvoboda Thanks, @gsmet pinged me about it, and pointed out that it started failing about 4 days back from 9th Dec, I had a look at commits and could not find anything obvious in the commit history...
I have to admit I'm not sure where in the Quarkus code I should look atround, so I'd appreciate some guidance where to start looking further, let me CC @geoand, @radcortez. My only idea right now, is to check if using @TestHttpResource annotation can do better

[sberyozkin]

OK, the plan is to go via https://github.com/quarkusio/quarkus/commits/main/test-framework, run the test against different code views, and try to narrow down something :-)

[rsvoboda]

@sberyozkin QS started to fail on Dec 6th

• https://github.com/quarkusio/quarkus-quickstarts/actions/workflows/native-build-development.yml
• last passing: https://github.com/quarkusio/quarkus-quickstarts/actions/runs/12172072155
• first failed: https://github.com/quarkusio/quarkus-quickstarts/actions/runs/12191800548

[rsvoboda]

I found it, it's caused by a47ad60 / #42715

cc @sberyozkin @gsmet @radcortez

[radcortez]

I'll have a look.

[sberyozkin]

Hey @rsvoboda Thanks a million, as I haven't got to it yet.

Thanks @radcortez, good news it is on main only :-)