You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/05/29 18:44:00 UTC

[jira] [Closed] (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 ]

Michael Osipov closed SUREFIRE-1572.
------------------------------------
    Resolution: Cannot Reproduce

Closing as it does not reappear anymore. If it does, retry with 3.1.0 and re-report. I will reopen.

> 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
(v8.20.10#820010)