Fix some additional build reproducibility issues in ArC by gsmet · Pull Request #53088 · quarkusio/quarkus

gsmet · 2026-03-16T20:50:04Z

No description provided.

quarkus-bot · 2026-03-16T20:50:10Z

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

description should not be empty, describe your intent or provide links to the issues this PR is fixing (using Fixes #NNNNN) or changelogs

_{This message is automatically generated by a bot.}

quarkus-bot · 2026-03-16T21:28:38Z

Status for workflow `Quarkus Documentation CI`

This is the status report for running Quarkus Documentation CI on commit 2418c6e.

✅ 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.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

github-actions · 2026-03-16T21:33:36Z

🎊 PR Preview 77f4dbb has been successfully built and deployed to https://quarkus-pr-main-53088-preview.surge.sh/version/main/guides/

Images of blog posts older than 3 months are not available.
Newsletters older than 3 months are not available.

quarkus-bot · 2026-03-17T01:46:01Z

Status for workflow `Quarkus CI`

This is the status report for running Quarkus CI on commit 2418c6e.

Failing Jobs

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	JVM Tests - JDK 17			Logs	Raw logs	🔍
✔️	JVM Tests - JDK 21			Logs	Raw logs	🔍
✔️	JVM Tests - JDK 25			Logs	Raw logs	🔍
✔️	JVM Tests - JDK 25 Semeru			Logs	Raw logs	🔍
❌	JVM Tests - JDK 17 Windows	`Build`	Failures	Logs	Raw logs	🔍
✔️	JVM Integration Tests - JDK 17			Logs	Raw logs	🔍
✔️	JVM Integration Tests - JDK 17 Windows			Logs	Raw logs	🔍
❌	JVM Integration Tests - JDK 21	`Build`	Failures	Logs	Raw logs	🔍
✔️	JVM Integration Tests - JDK 25			Logs	Raw logs	🔍
✔️	JVM Integration Tests - JDK 25 Semeru			Logs	Raw logs	🔍

You can consult the Develocity build scans.

Failures

⚙️ JVM Tests - JDK 17 Windows #

- Failing: extensions/panache/hibernate-orm-panache-kotlin/runtime extensions/panache/hibernate-reactive-panache-kotlin/runtime extensions/panache/mongodb-panache-kotlin/runtime and 2 more
! Skipped: extensions/panache/hibernate-orm-panache-kotlin/deployment extensions/panache/hibernate-reactive-panache-kotlin/deployment extensions/panache/mongodb-panache-kotlin/deployment and 5 more

📦 extensions/panache/hibernate-orm-panache-kotlin/runtime

❌ Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:2.3.10:test-compile (test-compile) on project quarkus-hibernate-orm-panache-kotlin: Compilation failure Failed connecting to the daemon in 4 retries

📦 extensions/panache/hibernate-reactive-panache-kotlin/runtime

❌ Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:2.3.10:kapt (kapt) on project quarkus-hibernate-reactive-panache-kotlin: Compilation failure Failed connecting to the daemon in 4 retries

📦 extensions/panache/mongodb-panache-kotlin/runtime

❌ Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:2.3.10:compile (compile) on project quarkus-mongodb-panache-kotlin: Compilation failure Failed connecting to the daemon in 4 retries

📦 extensions/resteasy-reactive/rest-client-kotlin-serialization/tests

❌ Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:2.3.10:test-compile (test-compile) on project quarkus-rest-client-kotlin-serialization-tests: Compilation failure Failed connecting to the daemon in 4 retries

📦 extensions/smallrye-reactive-messaging/deployment

❌ Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:2.3.10:test-compile (test-compile) on project quarkus-messaging-deployment: Compilation failure Failed connecting to the daemon in 4 retries

⚙️ JVM Integration Tests - JDK 21 #

- Failing: integration-tests/elytron-security-jdbc

📦 integration-tests/elytron-security-jdbc

❌ Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.5.4:test (default-test) on project quarkus-elytron-security-jdbc-integration-test:

See /home/runner/work/quarkus/quarkus/integration-tests/elytron-security-jdbc/target/surefire-reports for the individual test results. See dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. There was an error in the forked process

mkouba · 2026-03-17T07:18:18Z

extensions/arc/deployment/src/main/java/io/quarkus/arc/deployment/ConfigBuildStep.java

        recorder.validateConfigProperties(
                configProperties.stream()
                        .filter(ConfigPropertyBuildItem::isRuntimeInit)
+                        .sorted(Comparator.comparing(ConfigPropertyBuildItem::getPropertyName))


@gsmet Are you sure this helps? Because Collectors.toSet() is an unordered collector...

+1, this itself is useless AFAICT

So, it helped, I did numerous runs, but I agree it might have been by luck and I need to make the Set an ordered one.

mkouba · 2026-03-17T07:28:03Z

extensions/arc/deployment/src/main/java/io/quarkus/arc/deployment/SyntheticBeansProcessor.java

-        Map<String, Function<SyntheticCreationalContext<?>, ?>> creationFunctions = new HashMap<>();
-        Map<String, Supplier<ActiveResult>> checkActiveSuppliers = new HashMap<>();
-
+        TreeMap<String, SyntheticBeanBuildItem> sortedBeans = new TreeMap<>();


TBH I don't understand this change. The ordering follows the ordering of List<SyntheticBeanBuildItem> syntheticBeans and the fact that we first store all beans in a sorted map would not make any difference, or?

The List<SyntheticBeanBuildItem> syntheticBeans is not ordered.

And when calling the recorders in random order, I had sometimes some changes in the ordering.

I can probably find the diff back to help showing what I was trying to fix but it will require some archeology :)

The List syntheticBeans is not ordered.

Isn't it? I thought that build steps are guaranteed to be executed in the same order 🤔.

So, they are not guaranteed to run in the same order because of parallelism. But that's not the problem here.

What we guarantee is that their result will be contributed in the same order to the list of build steps. Which you would think would be enough in this case, except you can have the following in a build step:

for (element in my hashset/map) { create a synthetic bean build item }

which happens, and then your order is not guaranteed.

I thought it would be better to enforce the order at this level rather than going through all the possible code paths creating synthetic beans and enforcing strong ordering there.

I'm not working on the simple project I was working until now, I'm iterating on all the quickstarts so you have all sorts of cases.

Also, I often have 3-4, sometimes 8 reproducible builds until I have one that is different.

Let me know if it makes more sense :).

which happens, and then your order is not guaranteed.

Ah, I see. Basically, a build step can produce the SyntheticBeanBuildItems in random order.

Here is what I was trying to solve here:

Looking at MultiBuildItem javadoc, it says it gets injected in a sorted order if the MultiBuildItem implements Comparable. That sounds like a proper solution, instead of sorting on each use site?

Looking at MultiBuildItem javadoc, it says it gets injected in a sorted order if the MultiBuildItem implements Comparable. That sounds like a proper solution, instead of sorting on each use site?

I have to admit that I completely missed this sentence in the javadoc of MultiBuildItem but it really looks like a proper solution. @gsmet WDYM?

Fix some additional reproducibility issues in ArC

2418c6e

gsmet requested review from Ladicek and mkouba March 16, 2026 20:50

gsmet temporarily deployed to ci March 16, 2026 20:50 — with GitHub Actions Inactive

quarkus-bot bot added the area/arc Issue related to ARC (dependency injection) label Mar 16, 2026

mkouba reviewed Mar 17, 2026

View reviewed changes

Conversation

gsmet commented Mar 16, 2026

Uh oh!

quarkus-bot bot commented Mar 16, 2026

Uh oh!

quarkus-bot bot commented Mar 16, 2026

Status for workflow Quarkus Documentation CI

Uh oh!

github-actions bot commented Mar 16, 2026

Uh oh!

quarkus-bot bot commented Mar 17, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Status for workflow Quarkus CI

Failing Jobs

Failures

⚙️ JVM Tests - JDK 17 Windows #

📦 extensions/panache/hibernate-orm-panache-kotlin/runtime

📦 extensions/panache/hibernate-reactive-panache-kotlin/runtime

📦 extensions/panache/mongodb-panache-kotlin/runtime

📦 extensions/resteasy-reactive/rest-client-kotlin-serialization/tests

📦 extensions/smallrye-reactive-messaging/deployment

⚙️ JVM Integration Tests - JDK 21 #

📦 integration-tests/elytron-security-jdbc

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Status for workflow `Quarkus Documentation CI`

quarkus-bot bot commented Mar 17, 2026 •

edited by github-actions bot

Loading

Status for workflow `Quarkus CI`