Skip to content
Advertisement

Maven build and maven-failsafe-plugin – The forked VM terminated without properly saying goodbye

I use Docker and https://github.com/fabric8io/docker-maven-plugin for my integration tests.

On my Windows 10 (after updating to Windows 10 1709) machine I faced the following error with my Maven 3.5.0 build:

JavaScript

Right now I have no idea what can be wrong, I don’t see any failures with my tests.

What can be a reason of this issue and how to solve it?

UPDATED

My project have the following configuration:

parent pom.xml:

JavaScript

sub-module pom.xml:

JavaScript

As you can see – I added

JavaScript

to the configuration of maven-surefire-plugin to my parent pom.xml but it didn’t help.

This is output for Maven build with -e and -X

JavaScript

This is the full detailed output log: https://files.fm/u/nfegb38f

Windows 10 1709 update

Right now I have thoughts that this issue can be potentially related to the Windows 10 1709 update… I use docker and https://github.com/fabric8io/docker-maven-plugin for my integrstion tests and found the following topic – https://github.com/docker/for-win/issues/1221 Something is definitely wrong with this update and virtualization…

Advertisement

Answer

I have the same problem and found three solutions which working for me:

Problem description

Problem is with maven plugin maven-surefire-plugin only in version 2.20.1 and 2.21.0. I checked and you use version 2.20.1.

Solution 1

Upgrade plugin version to 2.22.0. Add in pom.xml:

JavaScript

Solution 2

Downgrade plugin version to 2.20. Add in pom.xml:

JavaScript

Solution 3

Use plugin configuration testFailureIgnore. Add in pom.xml:

JavaScript
Advertisement