RFR: JDK-8324930: java/lang/StringBuilder problem with concurrent jtreg runs

Aleksey Shipilev shade at openjdk.org
Tue Jan 30 17:23:31 UTC 2024


On Tue, 30 Jan 2024 09:08:28 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:

> On some Windows machines we see sometimes OOM errors because of high resource (memory/swap) consumption. This is especially seen when the jtreg runs have higher concurrency. A solution is to put the java/lang/StringBuilder tests in the exclusiveAccess.dirs group so that they are not executed concurrently, which helps to mitigate the resource shortages.
> Of course this has the downside that on very large machines the concurrent execution is not done any more.

Can we maybe see if we can fix these tests without exclusive-accessing them? I find it surprising that `java/lang/StringBuilder` tests are problematic, but `java/lang/StringBuffer` tests are not. Which tests fail?

-------------

PR Review: https://git.openjdk.org/jdk/pull/17625#pullrequestreview-1851921699


More information about the core-libs-dev mailing list