Dial down GetStackTraceALotWhenBlocking and GetStackTraceALotWhenPinned as they make slow progress when executed concurrently on under power systems. GetStackTraceALotWhenBlocking has 3 busy threads, GetStackTraceALotWhenPinned has two spinning threads. When they run concurrently in jdk/:tier1_part1 then they compete for CPU cycles on systems with a small number of cores, specifically the macOS systems in CIs and GHA that have only 4 cores, and make slow progress.
Both tests are also changed to fail eagerly if the main thread is interrupted by jtreg. Also the progress output of both tests is adjusted to print a progress message every second if possible. ------------- Commit messages: - Initial commit Changes: https://git.openjdk.org/jdk/pull/22193/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22193&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8344143 Stats: 28 lines in 2 files changed: 17 ins; 4 del; 7 mod Patch: https://git.openjdk.org/jdk/pull/22193.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22193/head:pull/22193 PR: https://git.openjdk.org/jdk/pull/22193
