[SUREFIRE-1056] fractional forkCount does not work as intended on single core machines

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.16
• Fix Version/s: 2.17
• Component/s: Maven Failsafe Plugin, Maven Surefire Plugin
• Environment: single core machines (repo with virtual machine)
• Assignee: Andreas Gudian
• Reporter: Ronald Chen
• Created: 28/Jan/14 17:24
• Updated: 04/Feb/14 12:40
• Resolved: 04/Feb/14 12:40

Description

We set forkCount=0.5C which works well for dual and quad core machines. We want to set something less than 1C since we want our development machines to continue to be usable while the test are running.

The problem comes in when a single core uses the 0.5C configuration, which is equivalent to forkCount=0.

forkCount=0 and forkCount=1 means vastly different things. forkCount=0 will run the test on the same JVM as the Maven processes, while forkCount=1 will fork 1 JVM.

In order for File.exists() to work (see java bug http://bugs.java.com/bugdatabase/view_bug.do;:YfiG?bug_id=4483097) the JVM working directory must be correctly set.

When forkCount=0 the Maven JVM working directory is used, thus test that use relative paths and File.exists() will fail.

What I expect is whenever a fractional forkCount is used, it is bounded to a minimum of 1. forkCount=0 should only be used when configured explicitly.