On Tue, 30 Jan 2024 09:08:28 GMT, Matthias Baesken <mbaes...@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. Hello Matthias, would you be able to include a stacktrace from one such failure? The tests you mention as failing: java/lang/StringBuilder/StringBufferRepeat.java java/lang/StringBuilder/CompactStringBuilderSerialization.java java/lang/StringBuilder/Insert.java are all "othervm" tests, so I'm curious what kind of OOM is being reported. ------------- PR Comment: https://git.openjdk.org/jdk/pull/17625#issuecomment-1925764255
