Lucene - Core
  1. Lucene - Core
  2. LUCENE-4002

Running tests with internal JVM diagnostic options (such as -verbose:*) will fail.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-ALPHA
    • Component/s: general/test
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      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.

        Activity

        Dawid Weiss created issue -
        Dawid Weiss made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Uwe Schindler made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Dawid Weiss
            Reporter:
            Dawid Weiss
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development