Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Sat, 3 Jun 2017 12:06:04 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13075489.1496001511000.359243.1496491564742@Atlassian.JIRA>
In-Reply-To: <JIRA.13075489.1496001511000@Atlassian.JIRA>
References: <JIRA.13075489.1496001511000@Atlassian.JIRA> <JIRA.13075489.1496001511513@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SUREFIRE-1376) "The forked VM terminated
 without properly saying goodbye" when running Surefire in a very deep
 project structure on Windows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sat, 03 Jun 2017 12:06:10 -0000


    [ https://issues.apache.org/jira/browse/SUREFIRE-1376?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
6035954#comment-16035954 ]=20

Hudson commented on SUREFIRE-1376:
----------------------------------

SUCCESS: Integrated in Jenkins build maven-surefire #1712 (See [https://bui=
lds.apache.org/job/maven-surefire/1712/])
[SUREFIRE-1376] "The forked VM terminated without properly saying (tibor17:=
 [http://git-wip-us.apache.org/repos/asf/?p=3Dmaven-surefire.git&a=3Dcommit=
&h=3D59c065f5d4a5a9c181ef9ce788b31305886e8592])
* (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefi=
re/booterclient/ForkConfiguration.java
* (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefi=
re/SurefireHelper.java
* (edit) maven-surefire-common/src/test/java/org/apache/maven/plugin/surefi=
re/SurefireHelperTest.java


> "The forked VM terminated without properly saying goodbye" when running S=
urefire in a very deep project structure on Windows
> -------------------------------------------------------------------------=
---------------------------------------------------
>
>                 Key: SUREFIRE-1376
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1376
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>    Affects Versions: 2.20
>         Environment: Windows
>            Reporter: Guillaume Bou=C3=A9
>            Assignee: Tibor Digana
>             Fix For: 2.20.1
>
>         Attachments: SUREFIRE-1376-prefix.patch
>
>
> When Surefire is ran on a project under a very long path (exceeding Windo=
ws' {{MAX_PATH}}), the invocation fails with
> {noformat}
> org.apache.maven.surefire.booter.SurefireBooterForkException: The forked =
VM terminated without properly saying goodbye. VM crash or System.exit call=
ed?
> {noformat}
> In the generated dumpstream, there is
> {noformat}
> # Created on 2017-05-28T10:17:09.474
> Error: Unable to access jarfile C:\Users\Guillaume\Desktop\surefire-longp=
ath-test-with-windows\surefire-longpath-test-with-windows\surefire-longpath=
-test-with-windows\surefire-longpath-test-with-windows\surefire-longpath-te=
st-with-windows\surefire-longpath-test-with-windows\target\surefire\surefir=
ebooter2512478076549179739.jar
> {noformat}
> The problem is that the path to the JAR file exceeds the maximum path len=
gth of 260 characters, and so it cannot be accessed.
> Prepending the path to the JAR file with {{&#92;&#92;?&#92;}}, [as docume=
nted on MSDN|https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#=
maxpath], makes the test run again correctly. I've attached a possible patc=
h with this approach (SUREFIRE-1376-prefix.patch, that also handles UNC pat=
hnames), but perhaps there is a better way to tackle this problem.
> In order to reproduce this, it is possible to create a project under lots=
 of different subdirectories, something like:
> {noformat}
> =E2=94=94=E2=94=80=E2=94=80=E2=94=80surefire-longpath-test-with-windows
>     =E2=94=94=E2=94=80=E2=94=80=E2=94=80surefire-longpath-test-with-windo=
ws
>         =E2=94=94=E2=94=80=E2=94=80=E2=94=80surefire-longpath-test-with-w=
indows
>             =E2=94=94=E2=94=80=E2=94=80=E2=94=80surefire-longpath-test-wi=
th-windows
>                 =E2=94=94=E2=94=80=E2=94=80=E2=94=80surefire-longpath-tes=
t-with-windows
>                     =E2=94=82   pom.xml
>                     =E2=94=82
>                     =E2=94=94=E2=94=80=E2=94=80=E2=94=80src
>                         =E2=94=94=E2=94=80=E2=94=80=E2=94=80test
>                             =E2=94=94=E2=94=80=E2=94=80=E2=94=80java
>                                 =E2=94=94=E2=94=80=E2=94=80=E2=94=80Test.=
java
> {noformat}
> As a side-note, this issue is behind the current Jenkins failures on [mav=
en-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8_windows|https://builds.apac=
he.org/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8_windows/3702/=
] when running the ITs on the Assembly Plugin.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)