Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Weekly building of Jakarta Platform Stand-alone TCKs...

On Mon, Jun 1, 2020 at 2:45 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
Just to see if this has any impact on the OOM, [5] is only building the standalone TCKS that are not part of the Platform TCK, which should reduce the amount of Jenkins job results to collect at the end.  

[5] seemed to be complete without hitting an OOM, so the next question is whether we need to raise the Java heap size or reduce the amount of Jenkins job results to avoid the OOM.

Scott
 

Scott

[5] https://ci.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run-master/48
On Mon, Jun 1, 2020 at 12:41 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
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



On Sat, May 30, 2020 at 2:21 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
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


Back to the top