I've reviewed the tests in `tests/jdk/java/lang/ProcessBuilder` for issues where a specific `launchMechanism` mode is explicitly requested for running a test, but is not honoured by other jvm processes spawned by the test runner.
Out of all tests present, I only found two issues: - In `Basic.java` where the specified value for `jdk.lang.Process.launchMechanism` isn't propagated to descendant java processes. - In `InvalidWorkDir.java`, where the posix_spawn test run incorrectly runs in fork mode. --------- - [x] I confirm that I make this contribution in accordance with the [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). ------------- Commit messages: - InvalidWorkDir test posix_spawn run uses fork mode - 8378583: (process) ProcessBuilder tests that span deeper trees must pass launchMechanism to their children Changes: https://git.openjdk.org/jdk/pull/31126/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=31126&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8378583 Stats: 14 lines in 2 files changed: 13 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/31126.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/31126/head:pull/31126 PR: https://git.openjdk.org/jdk/pull/31126
