WildFly build fails on centos 6.4

[citisolo]

During the build I get these results

...

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 19:04.097s

[INFO] Finished at: Mon Jul 29 18:39:08 BST 2013

[INFO] Final Memory: 281M/710M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project wildfly-arquillian-container-embedded: There are test failures.

[ERROR]

[ERROR] Please refer to /home/redbandit/src/JBoss/wildfly-8.0.0.Alpha3-src/arquillian/container-embedded/target/surefire-reports for the individual test results. ...

the log file reports the following error which seems to be caused by the ArchiveDeployer module;

-------------------------------------------------------------------------------

Test set: org.jboss.as.arquillian.container.embedded.CdiTestCase

-------------------------------------------------------------------------------

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 19.568 sec <<< FAILURE!

org.jboss.as.arquillian.container.embedded.CdiTestCase  Time elapsed: 0 sec  <<< ERROR!

org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war

    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)

    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)

    at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)...

I'm fairly new to the jboss/platform so this doesn't mean much to me but I was wondering if anybody out there can make sense of this ?

[nickarls]

There is no log anywhere what *actually* went wrong in the test deployment?

[ctomc]

Open

arquillian/container-embedded/target/jbossas/standalone/log/server.log

there you will be able to see what the problem is.

or you can post contents of that file here.

Anyhow there should be no special issues building WildFly on Centos/RHEL 6.4 as that is one of the platforms our CI uses to test the code.

--

tomaz

[citisolo]

Thanks niklas for the quick response. I have been able to resolve the issue . What happened is that I first downloaded the EAP version and ran it on my machine . when I realized that it was the AS7 version that I wanted I shut down the EAP version using the command script and downloaded and attempted to build wildfly . It turns out that the EAP was had processes still running in the background . I manually killed the processes and the build was successful soon after !

What I did want to ask out of curiosity is why those background processes were still running after I shut down the server ? Did I do something wrong ? I used the script {JBOSS_HOME}/bin/jboss-cli.sh --connect command=:shutdown

[nickarls]

Hard to tell. In any case there shouldn't be more than one java process for the AS.