Uploaded image for project: 'WildFly Elytron'
  1. WildFly Elytron
  2. ELY-1457

Unable to run testsuite using mvn surefire:test

XMLWordPrintable

    • Hide 
      mvn clean install -DskipTests
mvn surefire:test -fae -Dmaven.test.failure.ignore=true

      Build failed with "VM crash or System.exit called?"

      Show
      mvn clean install -DskipTests mvn surefire:test -fae -Dmaven.test.failure.ignore=true Build failed with "VM crash or System.exit called?" 

      mvn clean install -DskipTests
mvn surefire:test -fae -Dmaven.test.failure.ignore=true

[WARNING] Corrupted stdin stream in forked JVM 1. See the dump file /home/mchoma/workspace/git-repositories/wildfly-elytron/target/surefire-reports/2017-11-30T17-02-48_325-jvmRun1.dumpstream

ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Command was /bin/sh -c cd /home/mchoma/workspace/git-repositories/wildfly-elytron && /usr/java/jdk1.8.0_131/jre/bin/java '-javaagent:${org.jmockit:jmockit:jar}' -jar /home/mchoma/workspace/git-repositories/wildfly-elytron/target/surefire/surefirebooter575191532113315054.jar /home/mchoma/workspace/git-repositories/wildfly-elytron/target/surefire 2017-11-30T17-02-48_325-jvmRun1 surefire4127140177271714029tmp surefire_06835135917194901533tmp
Error occurred in starting fork, check output in log
Process Exit Code: 1
      • "mvn test" works just fine.
      • "mvn surefire:test" used to be necessary for running testsuite with IBM JDK, as TS was not compilable with IBM JDK (this is not true anymore). So TS was build with Oracle JDK and run with IBM JDK.
      • "mvn surefire:test" used to work back in July.

              jucook Justin Cook (Inactive)
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: