Rewrite the Vert.x MDC tests to be more robust

[cescoffier]

@gsmet as requested, let's see how it goes....

My rewrite does not call a remove service (which can be very slow and stop responding).

[cescoffier]

I don't believe the CI ran successfully... @gsmet @geoand any idea?

[cescoffier]

Quarkus CI / JVM Tests - JDK 17 (pull_request) Successful in 3m ..... yeah sure....

[cescoffier]

ah no, it only ran the updated modules... nice!

[geoand]

Yeah, that's the GIB Maven extension (from @famod) at work :)

[gsmet]

I will rerun them once to have another run.

[gsmet]

Doesn't look good ^

[cescoffier]

Yeah... I will have another look tomorrow. I was hoping it was the remote service, but it's not.

I need to look under the hood, it might be a real bug, not just a test issue.

[quarkus-bot]

---

🌘 This workflow status is outdated as a new workflow run has been triggered.

---

Failing Jobs - Building 21d78e5

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✖	JVM Tests - JDK 11	Build	Failures	Logs	Raw logs
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs
✖	JVM Tests - JDK 17 Windows	Build	Failures	Logs	Raw logs
✖	JVM Tests - JDK 20	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 #

- Failing: extensions/vertx/deployment 

📦 extensions/vertx/deployment

✖ io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode line 45 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Assertion condition defined in void io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode() log doesn't contain: Received HTTP request ### 55088c77-bd7b-46d2-b327-64b7ec645b76 ==> expected: <true> but was: <false> within 2 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)

---

⚙️ JVM Tests - JDK 17 #

- Failing: extensions/vertx/deployment 

📦 extensions/vertx/deployment

✖ io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode line 45 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Assertion condition defined in void io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode() log doesn't contain: Received HTTP request ### 92760c3b-da8c-4080-9a25-78b641180e9b ==> expected: <true> but was: <false> within 2 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)

---

⚙️ JVM Tests - JDK 17 Windows #

- Failing: extensions/vertx/deployment 

📦 extensions/vertx/deployment

✖ io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode line 45 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Assertion condition defined in void io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode() log doesn't contain: Received HTTP request ### 2214f438-d661-455b-a580-29e18ac6e59d ==> expected: <true> but was: <false> within 2 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)

---

⚙️ JVM Tests - JDK 20 #

- Failing: extensions/vertx/deployment 

📦 extensions/vertx/deployment

✖ io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode line 45 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Assertion condition defined in void io.quarkus.vertx.mdc.VertxMDCDevModeTest.mdcDevMode() log doesn't contain: Received HTTP request ### c4ea2097-2f71-44a0-b0d2-ed1072775500 ==> expected: <true> but was: <false> within 2 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)

[cescoffier]

We had a green build.
I ran the windows tests again to ensure it was not just chance.

I just started the whole pipeline again to see.

---

The PR:

• removes the external service. It can be slow or even block our requests (rate limiting / blacklisting)
• makes sure we wait for the log handler to be in the delayed handler list before starting to execute the tests

[quarkus-bot]

✔️ 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.

[cescoffier]

Another green run, let's merge and see if I need to revisit them again later.