[
https://issues.apache.org/jira/browse/LUCENE-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss resolved LUCENE-4002.
---------------------------------
Resolution: Fixed
Fixed by randomizedtesting 1.4.0
> Running tests with internal JVM diagnostic options (such as -verbose:*) will
> fail.
> ----------------------------------------------------------------------------------
>
> Key: LUCENE-4002
> URL: https://issues.apache.org/jira/browse/LUCENE-4002
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/test
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Fix For: 4.0
>
>
> Passing JVM options that dump something to output streams before they are
> intercepted (-verbose:gc, -verbose:class) will break the communication
> between the runner and the master.
> Currently junit4 communicates with forked processes via stdout or stderr
> (depending on the JVM and which stream the JVM uses to dump crash infos).
> This is done for efficiency since it's a natural blocking pipe between the
> two processes. I forgot that the jvm can:
> 1) use process streams to dump verbose logs (gc, classes, jit),
> 2) use process streams directly, bypassing System.* overrides, to dump
> warnings.
> This can be solved my moving the communication layer to another pipe or to a
> socket. I'll play with the options.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
