Native TS: integration-tests/quartz leaves hanging processes

[Karm]

Describe the bug

It seems that the TS leaves hanging Quartz runner processes. At least when executed with builder image and in native mode. It becomes apparent on a system that is not re-provisioned for each TS run, e.g.:

tester    120723  0.0  1.4 5122972 360856 ?      Sl   Aug31  15:15 /home/tester/quarkus/integration-tests/quartz/target/quarkus-integration-test-quartz-2.7.6.Final-runner -Dquarkus.http.port=8081 -Dquarkus.http.ssl-port=8444 -Dtest.url=http://localhost:8081 -Dquarkus.log.file.path=/home/tester/quarkus/integration-tests/quartz/target/quarkus.log -Dquarkus.log.file.enable=true
tester    269017  0.0  1.4 5122972 347316 ?      Sl   Sep01  14:44 /home/tester/quarkus/integration-tests/quartz/target/quarkus-integration-test-quartz-2.7.6.Final-runner -Dquarkus.http.port=8081 -Dquarkus.http.ssl-port=8444 -Dtest.url=http://localhost:8081 -Dquarkus.log.file.path=/home/tester/quarkus/integration-tests/quartz/target/quarkus.log -Dquarkus.log.file.enable=true
tester    456872  0.0  1.4 4464060 347228 ?      Sl   Sep19   1:04 /home/tester/quarkus/integration-tests/quartz/target/quarkus-integration-test-quartz-2.13.0.CR1-runner -Dquarkus.http.port=8081 -Dquarkus.http.ssl-port=8444 -Dtest.url=http://localhost:8081 -Dquarkus.log.file.path=/home/tester/quarkus/integration-tests/quartz/target/quarkus.log -Dquarkus.log.file.enable=true
tester    

The good new is the process survived since August. The bad news is that this should not be happening.
I will take a look at what the Quartz TS does and why this happens unless someone well versed in Quartz beats me to it.

Expected behavior

TS does not leave any hanging processes.

Actual behavior

Quartz native executable runner left.

How to Reproduce?

#!/bin/sh
export CONTAINER_RUNTIME=podman
export JAVA_HOME="/usr/java/openjdk-11"
export PATH="${JAVA_HOME}/bin:${PATH}"
export BUILDER_IMAGE_WITHOUT_TAG=<mandrel builder image>
export BUILD_DISPLAY_NAME=<mandrel builder image tag>
export QUARKUS_VERSION=2.13.0.CR1
export QUARKUS_REPO=https://github.com/quarkusio/quarkus.git
export QUARKUS_MODULES="\
!bouncycastle-fips-jsse,\
!container-image/quarkus-standard-way,\
!devtools,\
!google-cloud-functions,\
!google-cloud-functions-http,\
!gradle,\
!hibernate-orm-panache-kotlin,\
!kotlin,\
!kotlin-serialization,\
!kubernetes-client,\
!kubernetes/maven-invoker-way,\
!maven,\
!mongodb-panache-kotlin,\
!mongodb-rest-data-panache,\
!rest-client-reactive-kotlin-serialization,\
!resteasy-reactive-kotlin,\
!smallrye-opentracing"

 ${CONTAINER_RUNTIME} pull ${BUILDER_IMAGE_WITHOUT_TAG}:${BUILD_DISPLAY_NAME}
 if [ "$?" -ne 0 ]; then
     echo There was a problem pulling the image ${BUILDER_IMAGE_WITHOUT_TAG}:${BUILD_DISPLAY_NAME}. We cannot proceed.
     exit 1
 fi
 ${CONTAINER_RUNTIME} run ${BUILDER_IMAGE_WITHOUT_TAG}:${BUILD_DISPLAY_NAME} --version
 if [ "$?" -ne 0 ]; then
     echo There was a problem running --version with  ${BUILDER_IMAGE_WITHOUT_TAG}:${BUILD_DISPLAY_NAME}. We cannot proceed.
     exit 1
 fi
 ${CONTAINER_RUNTIME} inspect ${BUILDER_IMAGE_WITHOUT_TAG}:${BUILD_DISPLAY_NAME}
 rm -rf quarkus
 git clone --quiet --depth 1 --branch ${QUARKUS_VERSION} ${QUARKUS_REPO}
 cd quarkus
 export MAVEN_OPTS="-Xmx5g -XX:MaxMetaspaceSize=4g"
 ./mvnw install -Dquickly
 ./mvnw verify -fae -f integration-tests/pom.xml -Dmaven.test.failure.ignore=true \
     -pl ${QUARKUS_MODULES} -Ddocker -Dnative \
     -Dquarkus.native.container-build=true \
     -Dquarkus.native.builder-image="${BUILDER_IMAGE_WITHOUT_TAG}:${BUILD_DISPLAY_NAME}" \
     -Dquarkus.native.container-runtime=${CONTAINER_RUNTIME} \
     -Dquarkus.native.native-image-xmx=10g

Output of uname -a or ver

Linux amd64

Output of java -version

Temurin-11.0.15+10

GraalVM version (if different from Java)

22.3 dev, Git head: 4407306f2505

Quarkus version or git rev

2.13.0.CR1, 2.7.6.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @Sgitario, @evanchooly, @galderz, @geoand, @iocanel, @jerboaa, @machi1990, @mkouba, @zakkak

[geoand]

I can confirm I see this. I'll check and see what is going on

[geoand]

#28118 takes care of it

[Karm]

I can reproduce it with the current main on my workstation too as:

$ C=5 while [ $C -ge 0 ];do ./mvnw verify -fae -f integration-tests/pom.xml -Dmaven.test.failure.ignore=true 
-pl quartz -Ddocker -Dnative -Dquarkus.native.container-build=true 
-Dquarkus.native.builder-image=<builder image> 
-Dquarkus.native.container-runtime=docker -Dquarkus.native.native-image-xmx=10g;let C=$C-1;done

$ ps aux | grep "quarkus.*quartz.*runner"
karm       48892  0.2  0.3 4032820 127580 pts/2  Sl   10:26   0:00 /home/karm/workspaceRH/quarkus/integration-tests/quartz/target/quarkus-integration-test-quartz-999-SNAPSHOT-runner -Dquarkus.http.port=8081 -Dquarkus.http.ssl-port=8444 -Dtest.url=http://localhost:8081 -Dquarkus.log.file.path=/home/karm/workspaceRH/quarkus/integration-tests/quartz/target/quarkus.log -Dquarkus.log.file.enable=true

[geoand]

Yup, there was an oversight in the test framework

[Karm]

#28118 takes care of it

Thanks @geoand , that was well within the under an hour SLA 😃 😃 😃

[geoand]

😆

[geoand]

#28119 is also related