[
https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100022#comment-16100022
]
Piotr Krokowski commented on SUREFIRE-1397:
-------------------------------------------
I've found out that using:
<workingDirectory>${test.run.dir}${surefire.forkNumber}</workingDirectory>
is workaround for the mentioned issue.
Please clarify, if such behavior is intended (I sincerly hope it's not:), or is
the race condition to be eliminated in further releases ?
> "ExecutionException Cannot create workingDirectory" occurs randomly when
> forkCount>1
> ------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1397
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1397
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19, 2.19.1, 2.20
> Reporter: Piotr Krokowski
> Attachments: debug-output.txt, pom.xml
>
>
> I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the
> plugin.
> It looks like the issue was introduced in 2.19.
> I'd kindly like to ask to fix this as soon as possible, as this is a blocker
> in adopting JUnit5!
> Steps to reproduce:
> - Have a simple project with at least two tests
> - Configure forkCount=2
> - Configure workingDirectory, eg. `${project.basedir}/target/test-run`
> - Run `mvn clean test -T 2`
> - Observe the exception (might occur randomly)
> I'm attaching the error message, full stack trace, and my example pom.xml,
> that I used to reproduce the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
