You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2017/12/08 14:24:11 UTC

[jira] [Closed] (OAK-6977) The oak-run process started by UpgradeIT interferes with Surefire

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

Davide Giannella closed OAK-6977.
---------------------------------

Bulk close 1.7.12

> The oak-run process started by UpgradeIT interferes with Surefire
> -----------------------------------------------------------------
>
>                 Key: OAK-6977
>                 URL: https://issues.apache.org/jira/browse/OAK-6977
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-tar
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>             Fix For: 1.7.12, 1.8
>
>
> Running {{UpgradeIT}} produces the following output.
> {noformat}
> [INFO] Running org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file C:\Users\Francesco\src\svn\oak\trunk\oak-segment-tar\target\failsafe-reports\2017-11-23T01-34-55_578-jvmRun1.dumpstream
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.772 s - in org.apache.jackrabbit.oak.segment.upgrade.UpgradeIT
> {noformat}
> According to SUREFIRE-1359, SUREFIRE-1410, and the [Maven Surefire Plugin FAQ|http://maven.apache.org/surefire/maven-surefire-plugin/faq.html], this is caused by the oak-run processes spawned by the test. In particular, the error is due to those processes being forked with their stdout/stdin inherited from the parent process.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)