Closed joedayz closed 9 years ago
Hi @joedayz
Can you please add more information? Which maven command are you running, environment, etc?
Hi @radcortez , I used it command according to the documentation:
$ mvn -Pwildfly-managed-arquillian,browser-firefox test
That command should instantiate a Wildfly container, but apparently in your case the server did not start. Can you please post the full build log?
Hi @radcortez:
I did test in a pc with windows 8.1, jdk 8:
https://gist.github.com/joedayz/67ed3182d6f50356ac01
In a Mac with Yosemite, jdk 1.7:
https://gist.github.com/joedayz/9e73b8e59b7de4bbb80e
I did the test many times and the result is error according to the links.
Jose
Hi @joedayz
Unfortunately I don't have any machine with a win8 env. I did try it with win7 and jdk 8 and it worked fine (except for test failures), but the container started up.
On Mac, it's working. You are having test failures. It's "normal", since tests may not be updated or the applications servers may be doing something different from what's expected in the spec. Anyway, run with the flag -fn so you can complete the build, or -Dmaven.test.skip=true.
Thanks @radcortez
Is this ok? Can we close the issue?
Yes. All is ok!! Thanks
Hi guys
I am getting this error in a new fresh installation.
Test set: org.javaee7.batch.chunk.checkpoint.BatchChunkCheckpointTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.02 sec <<< FAILURE! - in org.javaee7.batch.chunk.checkpoint.BatchChunkCheckpointTest org.javaee7.batch.chunk.checkpoint.BatchChunkCheckpointTest Time elapsed: 5.019 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container java.util.concurrent.TimeoutException: Managed server was not started within 60 s