Skip to content

Resolve extension catalog from a registry that provided platform stream metadata#52521

Merged
gsmet merged 1 commit intoquarkusio:mainfrom
aloubyansky:stream-from-registry
Feb 11, 2026
Merged

Resolve extension catalog from a registry that provided platform stream metadata#52521
gsmet merged 1 commit intoquarkusio:mainfrom
aloubyansky:stream-from-registry

Conversation

@aloubyansky
Copy link
Member

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.

@quarkus-bot quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/platform Issues related to definition and interaction with Quarkus Platform labels Feb 10, 2026
@quarkus-bot
Copy link

quarkus-bot bot commented Feb 10, 2026

Status for workflow Quarkus CI

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

Failing Jobs

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)

@gsmet
Copy link
Member

gsmet commented Feb 11, 2026

@holly-cummins

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)

looks suspicious

@gsmet gsmet merged commit bb112af into quarkusio:main Feb 11, 2026
65 of 66 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.32 - main milestone Feb 11, 2026
@holly-cummins
Copy link
Contributor

@holly-cummins

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)

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.

@holly-cummins
Copy link
Contributor

Actually, the Devolocity history (or just looking at the timestamps on this CI) exonerates #52529, because this failed before the merge. #52432 is still suspicious, though, because Alexey's branch did include that commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/platform Issues related to definition and interaction with Quarkus Platform triage/flaky-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants