(process) ProcessBuilder tests that span deeper trees must pass launchMechanism to their children

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • tbd
    • Affects Version/s: 27
    • Component/s: core-libs

      I strongly suspect that a bunch of ProcessBuilder tests are a bit faulty - most test multiple launchMechanism modes, which is okay, but some of them, during testing, span process trees of three layers or more, and those child JVMs must also get passed the launchMechanism, otherwise we repeatedly just test the POSIX_SPAWN mode.

      The typical reason for using deeper trees is to pass an environment variable to the middle process (not possible, easily, in-process in the outermost test JVM), or to test stderr redirection.

      I think at least affected are:
      - Basic.java (the redirectIO test part)
      - JspawnHelperProtocol (see parentCode())

            Assignee:
            Frederic Thevenet
            Reporter:
            Thomas Stuefe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: