Hang in clustering test GroupListenerTestCase test

During the running org.jboss.as.test.clustering.cluster.group.GroupListenerTestCase test named `test`, a forked maven test was stuck: https://github.com/wildfly/wildfly/blob/main/testsuite/integration/clustering/src/test/java/org/jboss/as/test/clustering/cluster/group/GroupListenerTestCase.java#L94. It looks like the process tried to start, then decided to destroy the server:

"main" #1 prio=5 os_prio=0 cpu=2960.57ms elapsed=4253.17s tid=0x00007fc9dc017800 nid=0x1da7 in Object.wait() [0x00007fc9e633e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(java.base@11.0.14/Native Method)

• waiting on <no object reference available>
  at java.lang.Object.wait(java.base@11.0.14/Object.java:328)
  at java.lang.ProcessImpl.waitFor(java.base@11.0.14/ProcessImpl.java:495)
• waiting to re-lock in wait() <0x00000000e6b351c0> (a java.lang.ProcessImpl)
  at org.wildfly.core.launcher.ProcessHelper.destroyProcess(ProcessHelper.java:60)
  at org.jboss.as.arquillian.container.CommonManagedDeployableContainer.startInternal(CommonManagedDeployableContainer.java:95)
  at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:131)
  at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:179)
  at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:137)
  at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:133)
  at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:208)
  at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:133)
  at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.14/Native Method)
  at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.14/NativeMethodAccessorImpl.java:62)
  at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.14/DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(java.base@11.0.14/Method.java:566)
  at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
  at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
  at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
  at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:54)
  at jdk.internal.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
  at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.14/DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(java.base@11.0.14/Method.java:566)
  at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
  at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
  at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
  at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
  at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
  at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:87)
  at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:72)
  at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:65)
  at org.jboss.as.test.clustering.cluster.AbstractClusteringTestCase.start(AbstractClusteringTestCase.java:233)
  at org.jboss.as.test.clustering.cluster.group.GroupListenerTestCase.test(GroupListenerTestCase.java:94)

Here is some output from the node-2 log:

2022-06-17 15:45:15,529 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool – 92) WFLYUT0021: Registered web context: '/GroupListenerTestCase' for server 'default-server'
2022-06-17 15:46:11,471 INFO [org.jboss.as.server] (Thread-1) WFLYSRV0220: Server shutdown has been requested via an OS signal

In particular I notice no WFLYSRV0010 for the deployment