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

Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2020/04/25 09:28:00 UTC

[jira] [Closed] (SUREFIRE-1780) Print JPMS errors from native stream of the fork JVM

     [ https://issues.apache.org/jira/browse/SUREFIRE-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana closed SUREFIRE-1780.
----------------------------------
    Resolution: Fixed

https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=e0304d973bcb24a020aa8fb0d05e6230b217a577

> Print JPMS errors from native stream of the fork JVM
> ----------------------------------------------------
>
>                 Key: SUREFIRE-1780
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1780
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: process forking
>         Environment: Java 9+
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M5
>
>
> When JVM prints own logs to the native stream, the surefire stream becomes corrupted. These are printed in a dump file and they are supposed a stream corruption. We can extract some special logs from this corrupted stream.
> This issue is based on the last discussion in SUREFIRE-1262.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)