On 05/02/2025 03:09, Chuck Caldarale wrote:
<snip/>
Didn’t Mark limit test JVMs to 256m in a recent commit:
diff --git a/build.xml b/build.xml
index f47b137d1c..bdb0b0cf7a 100644
--- a/build.xml
+++ b/build.xml
@@ -2043,7 +2043,8 @@
errorproperty="test.result.error"
failureproperty="test.result.failure"
haltonfailure="${test.haltonfailure}"
- threads="${test.threads}">
+ threads="${test.threads}"
+ maxmemory="256m">
<jvmarg value="${test.jvmarg.egd}"/>
<jvmarg value="-Dfile.encoding=UTF-8"/>
Sorry this is causing issues. I thought 256m would be plenty and I
didn't see any issues with my local testing. The issue I had was that
with lots of test threads (60) the OS in my test VM was running out of
memory because each Java instance was reserving more than it needed.
I'll see if I can make this configurable, restore the old default and
then configure this locally.
I'll also take a look at the failing tests to see if there are any
opportunities to use memory more efficiently.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
