You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marcus Ackermann (JIRA)" <ji...@apache.org> on 2018/09/18 07:41:00 UTC
[jira] [Updated] (SUREFIRE-1572) Found dump files in
surefire-reports folder
[ https://issues.apache.org/jira/browse/SUREFIRE-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Ackermann updated SUREFIRE-1572:
---------------------------------------
Affects Version/s: 2.22.0
Environment: Java 1.8
> Found dump files in surefire-reports folder
> -------------------------------------------
>
> Key: SUREFIRE-1572
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1572
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.22.0
> Environment: Java 1.8
> Reporter: Marcus Ackermann
> Priority: Major
> Attachments: 2018-09-17T15-28-03_759-jvmRun1.dump, 2018-09-17T15-28-41_096-jvmRun1.dump
>
>
> After updating the surefire-plugin from 2.19.1 to 2.22.0 there are dump files in the folder {{surefire-reports}}. This behavior is non-deterministig. The maven build does not fail, and there is nothing written into {{testing.log}}.
> This seems to be related to the new _monitoring_ mechanism for the forked VM introduced in 2.20.1 with SUREFIRE-1302.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)