Hank Grabowski (a04acae1) at 02 Nov 20:23
I'm trying to do the full mvn clean test
build on Apple Silicon running OpenJDK 17. This test fails with a potential out of memory bug even when I have MVN_OPTS set as high as -Xmx16G -Xms16G
(the physical RAM of the system). The same build on ARM64 Ubuntu Linux running OpenJDK 17 with just 4 GB of physical RAM succeeds without problems. If I run the test individually then it does not have this problem. For other build reasons the last build configuration issues I can successfully get going is the one for the 11.3.3. I've attached the error output from the Maven run and the dump file that it references: ErrorOutput.txtdump.txt
This was for the 12.0 RC 1 as well as the head of the develop branch.
Closes #1252
Hank Grabowski (a04acae1) at 02 Nov 04:09
Fix issue #1252 by cleaning up Test Threadpools on completion.
... and 2702 more commits
The problem appears to be that several of the tests weren't cleaning up their thread pools. So over time the number of threads the VM had was going into the thousands. On Windows where the limit is unlimited, and Linux where the limit is ~30,000, this wasn't a problem. The current limit on macOS is 4096 which was being crossed. I'm submitted an MR that fixes this.
Hank Grabowski (dc9df985) at 02 Nov 03:55
Merge branch 'ci-cd-load-optimization' into 'develop'
... and 2669 more commits
I tried it with OpenJDK 8, 17, and 21. I also tried it for JUnit 5.9 instead of 5.10, per @bryan suggestion in the forum. That didn't seem to make a difference.
I'm trying to do the full mvn clean test
build on Apple Silicon running OpenJDK 17. This test fails with a potential out of memory bug even when I have MVN_OPTS set as high as -Xmx16G -Xms16G
(the physical RAM of the system). The same build on ARM64 Ubuntu Linux running OpenJDK 17 with just 4 GB of physical RAM succeeds without problems. If I run the test individually then it does not have this problem. For other build reasons the last build configuration issues I can successfully get going is the one for the 11.3.3. I've attached the error output from the Maven run and the dump file that it references: ErrorOutput.txtdump.txt
This was for the 12.0 RC 1 as well as the head of the develop branch.
If we know the version or approximate time period of this it could be helpful to state it explicitly.