PiT 25.1: skeleton-starter-flow-cdi last for ever when building

[manolo]

Description of the bug

When building skeleton-starter-flow-cdi the server never starts, it stacks saying:

[INFO] --- wildfly-maven-plugin:5.1.5.Final:start (start) @ project-base-flow-cdi ---
[INFO] Provisioning default server in /Users/manolo/Github/platform/PiT/platform-in-test-script/tmp/skeleton-starter-flow-cdi/target/server

Expected behavior

It builds

Minimal reproducible example

git clone -q git@github.com:vaadin/skeleton-starter-flow-cdi.git
cd skeleton-starter-flow-cdi
./mvnw clean install -Pproduction -Pit

Versions

• Vaadin / Flow version: 25.0 & 25.1

[manolo]

It also stays for ever when running in dev mode:

./mvnw wildfly:run -Pdevelopment

Though some times it gives an error (its random that get stacked or fails with the error):

.unsupported/sun.reflect=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-modules=java.se
[INFO] STANDALONE server is starting up.
10:34:43,151 INFO  [org.jboss.modules] (main) JBoss Modules version 2.1.6.Final
10:35:13,355 INFO  [org.jboss.msc] (main) JBoss MSC version 1.5.6.Final
10:35:13,361 INFO  [org.jboss.threads] (main) JBoss Threads version 3.9.1
10:35:13,407 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly 38.0.1.Final (WildFly Core 30.0.0.Final) starting
10:35:13,507 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
	at org.jboss.as.controller@30.0.0.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125)
	at org.jboss.as.server@30.0.0.Final//org.jboss.as.server.ServerService.boot(ServerService.java:386)
	at org.jboss.as.controller@30.0.0.Final//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:360)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.io.FileNotFoundException: /private/tmp/skeleton-starter-flow-cdi/target/server/standalone/configuration/standalone.xml (No such file or directory)
	at java.base/java.io.FileInputStream.open0(Native Method)
	at java.base/java.io.FileInputStream.open(FileInputStream.java:272)
	at java.base/java.io.FileInputStream.<init>(FileInputStream.java:203)
	at org.jboss.as.controller@30.0.0.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:110)
	... 3 more

10:35:13,508 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone.xml - Minimum feature stability level: community
10:35:13,511 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0050: WildFly 38.0.1.Final (WildFly Core 30.0.0.Final) stopped in 1ms

[mcollovati]

Cannot reproduce locally with the given instructions.
Servlet container starts, the application is deployed and tests run successfully

EDIT: tested with both 25.0 and 25.1

[manolo]

Thanks for testing, I'm using mac, will try with different system

[ZheSun88]

works on windows too.

[manolo]

After some investigation, the problem is that WildFly maven plugin lasts for ever when installing the application server if not installed already in the system.
We have changed the PiT Action to preinstall it, and then the pit script to pass JBOSS_HOME when running tests.
Not a problem in flow, closing this.

See:
vaadin/platform-in-test-script@673035d
vaadin/platform-in-test-script@67d6f4f
vaadin/platform-in-test-script@4649713

vaadin/platform#8668