[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cbi-dev] OOM in Standalone TCK build job and question about where do the default NLP_PROTOCOL_OPTS settings get configured?
|
Hi Scott,
Unfortunately, job [2] is a freestyle job, so you cannot override it by yourself. Two options: - you either move to a pipeline job (probably with just a jnlp container in the pod template) and you do the same kind of trick as you did for [2],
- or we increase the value for all your freestyle jobs on your instance. It means that each build will consume more resources and may block other jobs from running until they complete (when you reach the higher end of your resources quota).
Which solution do you prefer? IMO, you should go with #1, it will give you greater control and freedom in tweaking resources for each jobs individually.
Cheers,
Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation 🐦 @mikbarbero
Hi,
I would like to understand what the container/VM memory size is that goes with the "OutOfMemoryError: Java heap space" failures we get collecting job results from standalonetck-nightly-build-run-master [1].
I do see from standalonetck-nightly-build-run-master/47/injectedEnvVars [2] that JNLP_PROTOCOL_OPTS contains -Xmx256m. Can we identify where the JNLP_PROTOCOL_OPTS setting is coming from for [2] and also understand how much memory is available for a possibly higher -Xmx256m?
Just for comparison, the [1] job launches [3] which requests (Java max of) -Xmx2048m to be used for JNLP, of a possible OS/container/VM max memory limit of 2176Mi (as controlled via [4]).
Scott
_______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cbi-dev
|
Attachment:
signature.asc
Description: Message signed with OpenPGP