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

[Jaikiran Pai]

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.

> What do you think about marking jtreg tests with higher memory requirements with a jtreg key like highmemusage ? This way we do not need to put these tests into the exclusiveAccess.dirs group, but get a way (only if needed) to execute those with high memory usage separately e.g. with lower concurrency.

`jtreg --help Tests` shows this (among other things):


Test Selection Options
                These options can be used to refine the set of tests to be
                executed.
...

    -exclude:<file> | -Xexclude:<file>
                    Provide a file specifying tests that should not be run

...

    -match:<file>   Provide a file specifying tests that can be run (inverse of
                    -exclude)



Maybe you could experiment with these options to exclude the `java/lang/StringBuilder` test directory from your high concurrency run and then only run those in a low concurrency run?

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

PR Comment: https://git.openjdk.org/jdk/pull/17625#issuecomment-1952574423