On Wed, 31 Jan 2024 00:48:35 GMT, Joe Darcy <[email protected]> wrote:
> 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? It is a bit arbitrary which tests fail. one day : java/lang/StringBuilder/StringBufferRepeat.java java/lang/StringBuilder/CompactStringBuilderSerialization.java java/lang/StringBuilder/Insert.java other day: java/lang/StringBuilder/HugeCapacity.java next day it might differ a bit. Maybe it would be sufficient to execute only the HugeCapacity test in a non concurrent way because this one seems to be especially resource hungry, but I am not aware how this would work in jtreg (I can only set whole directories). Currently we run with this patch and the issues are gone. Is there a way to balance resource usage in jtreg runs? ------------- PR Comment: https://git.openjdk.org/jdk/pull/17625#issuecomment-1918595685
