On Tue, 19 Aug 2025 03:31:55 GMT, SendaoYan <s...@openjdk.org> wrote:
>> It is also something that can be changed later, in a follow up fix. > > Take test > test/hotspot/jtreg/compiler/arraycopy/stress/TestStressArrayCopy.java as > example. > If there is a bug in jvm with -Xcomp option which will cause this test run > time outed. Before this PR, it will take `7200*10` seconds to run this test > finish and report time outed failure. But after this PR, it will take > `28800*10` seconds to run this test finish ang then report timed out failure. > I think the `28800*10` senonds is too long and it's unacceptable. > It is unclear to me if the author meant this to be 2.5 more than normal or 10 > more than JTREG default, or a multiplier that seems to work. What matters is that the actual timeout, in seconds, remains unchanged, so please address this. Timeouts that are excessively long waste machine resources. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/26749#discussion_r2284090715
