The GitHub Actions job "CI" on grails-core.git/7.0.x has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 0cf1b9cb238b916ea8c2c31de640c91a067437d9 / Scott Murphy Heiberg <[email protected]> [skip tests] test: wait for the stopped process to exit in RunningApplicationProcessSpec stop() terminates the process through its ProcessHandle, and on Windows a ProcessHandle judges the process by its exit code. TerminateProcess records that code as soon as termination starts, so onExit() completes and stop() returns STOPPED while Windows is still tearing the process down. The spec then asked the Process whether it was alive, and on Windows that waits for the process object to be signalled, which happens only once the teardown ends. The Windows JDK 25 build caught the gap: !process.isAlive() || | || true |Process[pid=7412, exitValue=1] The exit value 1 is the code destroy() terminates with, read in the same instant isAlive() still answered true. The spec now waits for the process to exit instead of requiring it to be gone already. (cherry picked from commit 10cf675644d096dcbb1fd13bcebc451f06a1eba6) Report URL: https://github.com/apache/grails-core/actions/runs/39304647851 With regards, GitHub Actions via GitBox
