On Wed, 8 Jul 2026 16:31:16 GMT, Artur Barashev <[email protected]> wrote:
>> done > > On 2nd thought, let's keep a timeout for the `visibility` test only. That > test spawns a new VM per a cipher suite, we'll think how to avoid this. The > `handshake` test should run fine with a default timeout. Looking at the implementation, both the visibility and handshake runs currently spawn a separate VM per test case. The visibility run uses all supported suites (~90 on my system), while the handshake run uses only the enabled suites (~30). Instead of increasing the timeout further, I can combine the visibility and handshake checks in the same child VM invocation. That would reduce the total number of forks from roughly 120 to 90 and should lower the overall execution time. With that change, I would keep the timeout at 480, as you suggested. What do you think? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/31812#discussion_r3549965132
