Make sure the ordering of Maven repos in tests matches the ordering of the repos in Mojos

[aloubyansky]

No description provided.

[quarkus-bot]

Failing Jobs - Building 9bf92f7

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 MacOS M1		Failures	Logs	Raw logs
✔️	JVM Tests - JDK 18

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 MacOS M1 #

- Failing: integration-tests/mongodb-devservices 

📦 integration-tests/mongodb-devservices

✖ io.quarkus.it.mongodb.BookResourceTest.health line 45 - More details - Source on GitHub

java.net.SocketTimeoutException: Read timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
	at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)

✖ io.quarkus.it.mongodb.BookResourceTest.testReactiveClients line 39 - More details - Source on GitHub

java.net.SocketTimeoutException: Read timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
	at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)

✖ io.quarkus.it.mongodb.BookResourceTest.testBlockingClient line 34 - More details - Source on GitHub

java.net.SocketTimeoutException: Read timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
	at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)

✖ io.quarkus.it.mongodb.BookResourceWithParameterInjectionTest.testInjectedClient line 31 - More details - Source on GitHub

java.net.SocketTimeoutException: Read timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
	at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)

✖ io.quarkus.it.mongodb.OtherProfileBookResourceTest.testBlockingClient line 14 - More details - Source on GitHub

java.net.SocketTimeoutException: Read timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
	at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)

[aloubyansky]

I've noticed these tests failing on MacOS in other PRs too.

[geoand]

I've noticed these tests failing on MacOS in other PRs too.

Yup, maybe we need to restart the runners @holly-cummins?

[geoand]

Does this fix a known issue?

[aloubyansky]

There is no existing issue on github it would resolve (afaik). There are two issues I wanted to fix:

1. The order of remote Maven repositories from active profiles configured in settings.xml in quarkus:generate-code[-test] and quarkus:build is different from the one we end up with resolving dependencies in test phases.
2. Outside Quarkus bootstrap, once the "Maven context" with its remote repos was initialized using the default settings, re-initializing the "Maven context" using custom settings based on the default user settings may loose some repos. I found it implementing some tools/features for the Quarkus platform.

[holly-cummins]

I've noticed these tests failing on MacOS in other PRs too.

Yup, maybe we need to restart the runners @holly-cummins?

We've got a zulip thread for this issue, but I'll convert it to an issue since I think this is going to be a slow burner: #28779.

I've restarted the runners, but sadly it didn't help. I also can't reproduce locally. My "best" analysis, from looking at the line of code which is failing, is that build pixies come in, remove the docker binary from the machine while the mongo tests run, and then sneak back and reinstate the docker binary. (Somewhere, Occam's razor has its razor-head in its razor-hands.)