On Thu, 11 Dec 2025 20:48:28 GMT, Alexey Ivanov <[email protected]> wrote:
>> Khalid Boulanouare has updated the pull request with a new target base due >> to a merge or a rebase. The pull request now contains 37 commits: >> >> - Merge branch 'pr/25971' into jdk-8360498 >> - Merge branch 'openjdk:master' into jdk-8360498 >> - Resolves confict for when there is a merge with jdk-8158801 >> - Merge branch 'openjdk:master' into jdk-8360498 >> - Removes not needed changes >> - Revert "Removes not needed changes" >> >> This reverts commit e76780d50cc390e35443dccb193cfbc9a1cec1cb. >> - Removes not needed changes >> - Removes extra white lines >> - Merge branch 'pr/25971' into jdk-8360498 >> - Merge branch 'pr/25971' into jdk-8360498 >> - ... and 27 more: https://git.openjdk.org/jdk/compare/59a937ac...900a7943 > > test/jdk/java/awt/Mixing/AWT_Mixing/MixingPanelsResizing.java line 85: > >> 83: try { >> 84: Process p = Runtime.getRuntime() >> 85: .exec(JAVA_HOME + "/bin/java FrameBorderCounter"); > > Did I already asked this question? > > Why can't the code in `FrameBorderCounter` be run in the same JVM? I'm pretty > sure it can be. > > It's like for a separate refactoring, yet I'd like to have a tracking bug for > getting rid of launching another process to count something that can be done > by executing `FrameBorderCounter.main` directly and ensuring the frame is > disposed of. I've submitted [JDK-8377916](https://bugs.openjdk.org/browse/JDK-8377916): *Run `FrameBorderCounter` in-process in `AWT_Mixing` tests*. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/26625#discussion_r2805606386
