On Wed, 24 Sep 2025 21:57:40 GMT, Phil Race <[email protected]> wrote:
>> " * Build jobs: 48" >> >> That's the build jobs from configure. >> I've often wondered about that since it is basically saying "I'm going to >> use everything". >> >> Is that somehow propagated to jtreg concurrency too ? >> Or are you building + testing in parallel ? >> >> If it takes 80 seconds for this test, I wonder why lots of other tests >> aren't also having a timeout problem when you run them ? >> Why is this test special ? >> Or was the removal of the timeout factor too optimistic ? >> Does any other test on your config come close to timeout ? > > What's the command you are using to run the tests ? > make test .... something .. ? >Is that somehow propagated to jtreg concurrency too ? Yes, jtreg executed via make will use the same concurrency. >Why is this test special ? It is the only test in the jdk_desktop group that modifies a class file in the JDK via instrumentation. For some similar tests in other areas, the timeouts were increased by [JDK-8260555](https://bugs.openjdk.org/browse/JDK-8260555). Check the links from JDK-8260555, there are a few additional timeout issues have been reported. >What's the command you are using to run the tests ? bash configure --with-boot-jdk=~/jdk/jdk-24 --with-jtreg=~/jtreg && make images make run-test TEST="jtreg:jdk_desktop" JTREG='VERBOSE=summary;KEYWORDS=!headful&!printer;REPEAT_COUNT=1' ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/27397#discussion_r2377231592
