Resolve extension catalog from a registry that provided platform stream metadata#52521
Conversation
Status for workflow
|
| Status | Name | Step | Failures | Logs | Raw logs | Build scan |
|---|---|---|---|---|---|---|
| ❌ | JVM Tests - JDK 17 | Build |
Failures | Logs | Raw logs | 🔍 |
| ✔️ | JVM Tests - JDK 21 | Logs | Raw logs | 🔍 | ||
| ✔️ | JVM Tests - JDK 21 Semeru | Logs | Raw logs | 🔍 | ||
| ✔️ | JVM Tests - JDK 25 | Logs | Raw logs | 🔍 |
Full information is available in the Build summary check run.
You can consult the Develocity build scans.
Failures
⚙️ JVM Tests - JDK 17 #
- Failing: extensions/hibernate-orm/deployment
! Skipped: extensions/flyway/deployment extensions/hibernate-envers/deployment extensions/hibernate-reactive/deployment and 17 more📦 extensions/hibernate-orm/deployment
❌ io.quarkus.hibernate.orm.config.packages.ConfigEntityPUAssigmentUsingInterfaceTest. line 40 - History - More details - Source on GitHub
Details
java.lang.AssertionError:
Expecting empty but was: ["Timed out trying to set fork join ClassLoader, this should never happen unless something has tied up a fork join thread before the app launched [Error Occurred After Shutdown]"]
at io.quarkus.hibernate.orm.config.packages.ConfigEntityPUAssigmentUsingInterfaceTest.lambda$static$2(ConfigEntityPUAssigmentUsingInterfaceTest.java:40)
Flaky tests - Develocity
⚙️ JVM Tests - JDK 21 Semeru
📦 extensions/micrometer-opentelemetry/deployment
❌ io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_Async - History
Expected metrics data to contain a single point, none found-org.opentest4j.AssertionFailedError
Details
org.opentest4j.AssertionFailedError: Expected metrics data to contain a single point, none found
at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:42)
at org.junit.jupiter.api.Assertions.fail(Assertions.java:143)
at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lastReadingDataPoint(MetricDataFilter.java:237)
at io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_Async(MicrometerTimedInterceptorTest.java:125)
looks suspicious |
It does, doesn't it? :( My first thought was that #52529 did touch classloaders in the areas of fork join pools. But looking at the Quarkus code more closely, it seems like it's more likely to be caused by #52432 and something like ... H2 hanging on start? Will investigate. |
When multiple registries are configured, when resolving an extension catalog for a platform stream, the registry that returned the platform stream metadata should be used to resolve the primary extension catalog.