|
Hi Scott,
Yes this issue is consistently occurring for some time where the
job fails at the last publish-junit-report stage after all the
bundles are copied.
I could not find how we can change the default injectedEnvVars for
this job. I am only familiar with changing the variables for the
pipeline jobs at the Jenkinsfile.
Could this issue be related to the commit :
https://github.com/eclipse-ee4j/jakartaee-tck/commit/00e67287cfbfee273942bfd29b7c41edc035e3d3.
Regards,
Alwin
On 30/05/20 11:51 PM, Scott Marlow
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
Hi Scott,
I will analyse the pending issues in the standalone TCK
build and ask
for help here once we have more details. Most of them would
be related
to the already created issues to remove the pruned techs.
Regards,
Alwin
On 26/05/20 8:07 PM, Scott Marlow wrote:
> Alwin also created
> https://github.com/eclipse-ee4j/jakartaee-tck/issues/293
for
> correcting the building of standalone TCKs as well.
Alwin, do you
> need help with jakartaee-tck/issues/293?
|
