Adding to the mystery, If I open [1] now, I no longer see the JNLP_PROTOCOL_OPTS environment variable setting that specifies -Xmx256m (I did save a copy of the web page with the -Xmx256m setting).
Since we do use the same
https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master, I'm not really sure if the OOM during collection of job results is on the Jenkins slave VM or if it could possibly be on the Jenkins server. The answer should be in the exception call stack [3]. If the OOM is in Jenkins server, we may need to create a Eclipse CI ticket to tune the [4] Jenkins config.
Scott
Hi Alwin, all,
I was just looking at the "java.lang.OutOfMemoryError: Java heap space" failure in standalonetck-nightly-build-run-master [1] , it looks like we have a max of 256mb used for the JNLP process according to injectedEnvVars [2], could someone please remind me where we are setting the environment variables for [2]? I'm thinking that we should go higher than -Xmx256m (512m or even 1-2g) in NLP_PROTOCOL_OPTS.
Thanks,
Scott
