[external : quarkus ] - status

Test failures are intermittent.
Jdk11 ( disabled `quarkus-documentation, quarkus-reactive-routes-deployment,quarkus-cli,quarkus-integration-test-no-awt,quarkus-avro-reload-test`, which failed in earlier build https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/627)

run twice and got different failures:
https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/638/console

```
11:38:20 [INFO] Quarkus - OpenTelemetry - Deployment ............... FAILURE [01:08 min]
11:38:20 [INFO] Quarkus - Kubernetes - Vanilla - Deployment ........ FAILURE [ 43.624 s]
11:38:20 [INFO] Quarkus - OpenShift Client - Deployment ............ FAILURE [ 13.009 s]
11:38:20 [INFO] Quarkus - Kubernetes Service Binding - Deployment .. FAILURE [ 18.364 s]
11:38:20 [INFO] Quarkus - Quarkus - Vert.x GraphQL - Runtime ....... FAILURE [ 11.223 s]
11:38:20 [INFO] Quarkus - SmallRye GraphQL - Runtime ............... FAILURE [ 15.403 s]
11:38:20 [INFO] Quarkus - SmallRye GraphQL Client - Runtime ........ FAILURE [ 13.791 s]
11:38:20 [INFO] Quarkus - Logging - JSON - Runtime ................. FAILURE [ 8.008 s]
11:38:20 [INFO] Quarkus - Logging - GELF - Runtime ................. FAILURE [ 11.957 s]
11:38:20 [INFO] Quarkus - Picocli - Runtime ........................ FAILURE [ 11.206 s]
11:38:20 [INFO] Quarkus - HTTP Google Cloud Functions - Runtime .... FAILURE [ 25.578 s]
11:38:20 [INFO] Quarkus - Google Cloud Functions - Runtime ......... FAILURE [ 9.781 s]
11:38:20 [INFO] Quarkus - AWT - Runtime ............................ FAILURE [ 15.308 s]
11:38:20 [INFO] Quarkus - Dev tools - Project Core Extension Codestarts FAILURE [01:00 min]
11:38:20 [INFO] Quarkus - Integration Tests - Class tranformer - Runtime FAILURE [ 9.939 s]
11:38:20 [INFO] Quarkus - Integration Tests - Shared library ....... FAILURE [ 5.921 s]
11:38:20 [INFO] Quarkus - Integration Tests - Common JPA entities .. FAILURE [ 9.539 s]
11:38:20 [INFO] Quarkus - Integration Tests - JPA - XML mapping - Modern Library A FAILURE [ 22.350 s]
```

https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/634

```
03:49:40 [INFO] Quarkus - OpenTelemetry - Deployment ............... FAILURE [02:32 min]
03:49:40 [INFO] Quarkus - Kubernetes - Openshift - Deployment ...... FAILURE [ 41.169 s]
03:49:40 [INFO] Quarkus - Kubernetes - Minikube - Deployment ....... FAILURE [ 36.838 s]
03:49:40 [INFO] Quarkus - OpenShift Client - Runtime ............... FAILURE [ 23.158 s]
03:49:40 [INFO] Quarkus - Flyway - Runtime ......................... FAILURE [ 56.797 s]
03:49:40 [INFO] Quarkus - Quarkus - Vert.x GraphQL - Runtime ....... FAILURE [ 37.313 s]
03:49:40 [INFO] Quarkus - SmallRye GraphQL - Runtime ............... FAILURE [ 39.396 s]
03:49:40 [INFO] Quarkus - Logging - JSON - Runtime ................. FAILURE [ 27.759 s]
03:49:40 [INFO] Quarkus - Logging - GELF - Deployment .............. FAILURE [01:01 min]
03:49:40 [INFO] Quarkus - Picocli - Runtime ........................ FAILURE [ 37.269 s]
03:49:40 [INFO] Quarkus - HTTP Google Cloud Functions - Runtime .... FAILURE [01:11 min]
03:49:40 [INFO] Quarkus - Google Cloud Functions - Runtime ......... FAILURE [01:01 min]
03:49:40 [INFO] Quarkus - AWT - Runtime ............................ FAILURE [ 33.675 s]
03:49:40 [INFO] Quarkus - Dev tools - Project Core Extension Codestarts FAILURE [ 27.674 s]
```

Review the two linked grinder_sandbox_new console runs and compare the differing failures on JDK 11, including the disabled Quarkus modules listed in the issue. Start by identifying whether the failures share a common cause across the reported deployment, runtime, and integration-test modules. Done means the intermittent failure source is identified and the affected test run is made reliable.

Written by the indexing model from the issue text.