More appropriate test application module initialization in QuarkusDevModeTest

[aloubyansky]

This fixes warnings running QuarkusDevModeTests, such as

[INFO] Running io.quarkus.devui.BuildMetricsTest
2024-11-28 23:51:03,005 WARN  [io.qua.boo.BootstrapAppModelFactory] (main) Expected project directory /home/aloubyansky/git/quarkus/extensions/vertx-http/deployment/target/quarkus-dev-mode-test18265132251066872043 does not match current project directory /home/aloubyansky/git/quarkus/extensions/vertx-http/deployment

by making sure the correct test application module is returned from ApplicationModel.getAppArtifact().

This should also fix issues reported in the comments of #44104

[aloubyansky]

The failures look related I'll have a look

[aloubyansky]

These failures aren't related. None of the failing tests is a QuarkusDevModeTest.

The issue with the previous failure was related to using a made up artifact ID for a test project. Now that the original (test containing module) artifact ID is used, the previous failure is fixed.

[aloubyansky]

I'll re-run the CI, just in case.

[geoand]

💪

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 9b4f338.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/websockets-next/deployment

✖ io.quarkus.websockets.next.test.telemetry.MicrometerWebSocketsOnBinaryMessageTest.testClientEndpoint_MultiTextReceived_MultiTextSent - History

• Assertion condition defined as a Lambda expression in io.quarkus.websockets.next.test.telemetry.MetricsAsserter 1 expectation failed. Response body doesn't match expectation. Expected: Key 'quarkus_websockets_server_connections_opened_total' with value '21' and direction 'null' Actual: \# TYPE jvm_threads_peak_threads gauge \# HELP jvm_threads_peak_threads The peak live thread count since the Java virtual machine started or peak was reset - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: 
Assertion condition defined as a Lambda expression in io.quarkus.websockets.next.test.telemetry.MetricsAsserter 1 expectation failed.
Response body doesn't match expectation.
Expected: Key 'quarkus_websockets_server_connections_opened_total' with value '21' and direction 'null'
  Actual: # TYPE jvm_threads_peak_threads gauge
# HELP jvm_threads_peak_threads The peak live thread count since the Java virtual machine started or peak was reset
jvm_threads_peak_threads 92.0
# TYPE jvm_memory_committed_bytes gauge

✖ io.quarkus.websockets.next.test.telemetry.MicrometerWebSocketsOnBinaryMessageTest.testServerEndpoint_broadcasting - History

• Assertion condition defined as a Lambda expression in io.quarkus.websockets.next.test.telemetry.AbstractWebSocketsOnMessageTest Expected 1, got 0 ==> expected: <true> but was: <false> within 5 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.websockets.next.test.telemetry.AbstractWebSocketsOnMessageTest Expected 1, got 0 ==> expected: <true> but was: <false> within 5 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
	at io.quarkus.websockets.next.test.telemetry.AbstractWebSocketsOnMessageTest.testServerEndpoint_broadcasting(AbstractWebSocketsOnMessageTest.java:414)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)