| Re: [jakartaee-tck-dev] committers: The jakartaeetck-nightly-run-master job will now prompt for the tests to run |
Some of those mail session failures MAY be fixed by adding -Ddeployment.resource.validation=false To the GlassFish startup. -----Original Message----- From: jakartaee-tck-dev-bounces@xxxxxxxxxxx <jakartaee-tck-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Marlow Sent: 30 June 2020 18:01 To: jakartaee-tck-dev@xxxxxxxxxxx Subject: Re: [jakartaee-tck-dev] committers: The jakartaeetck-nightly-run-master job will now prompt for the tests to run On 6/29/20 3:00 PM, Scott Marlow wrote: > >> Will try the 6gb out via >> https://github.com/eclipse-ee4j/jakartaee-tck/pull/346 while waiting >> for feedback. > > 6gb might of been too big (jenkins spent an hour trying to obtain a > Kubernetes node to run tests on, which seemed to be stuck), trying 3gb > now for the JNLP memory size. > > https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/735/ > seems to be running okay, will see if the memory increase has any > impact on the jpa_appmanagedNoTx jobs. Switching to the 3gb memory size did seem to show an improvement, as the "jpa_appmanagedNoTx" tests are now https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-nightly-run-master/52/testReport/ shows the current results. Scott > > Scott > _______________________________________________ jakartaee-tck-dev mailing list jakartaee-tck-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev