Details
-
Bug
-
Resolution: Invalid
-
Medium
Description
By default, maven creates process forks for running tests. When I run such a maven build on Bitbucket Pipelines, I get the following error:
[ERROR] Please refer to /opt/atlassian/pipelines/agent/build/persistence/target/failsafe-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream. [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /opt/atlassian/pipelines/agent/build/persistence && /usr/lib/jvm/java-1.8-openjdk/jre/bin/java -jar /opt/atlassian/pipelines/agent/build/persistence/target/surefire/surefirebooter6575592553579584591.jar /opt/atlassian/pipelines/agent/build/persistence/target/surefire 2018-01-13T12-32-13_138-jvmRun1 surefire4725132626445902495tmp surefire_05599682100559927811tmp [ERROR] Error occurred in starting fork, check output in log [ERROR] Process Exit Code: 1
Is Bitbucket Pipelines preventing the creation of process forks or killing forks automatically? Is there any way of accessing the failsafe-reports under /opt/atlassian/pipelines/agent/build/persistence/target/failsafe-reports? These might reveal more details about the problem.