As you probably saw I have disabled the auth related tests and the JDBC module builds seem to be running more reliably so far
Rob On 05/10/2013 13:28, "Andy Seaborne" <[email protected]> wrote: >On 30/09/13 10:25, Rob Vesse wrote: >> Potentially useful hint from the Marmotta list about the cause of the >> random maven JVM terminations >> >> Rob > >I've changed "test" and "deploy" to have -Xrs. We can see how it goes. > > >Sorry to come back to this but other main cause of instability is >TestRemoteEndpointResultsWithAuth. > >My other through is to run less tests. Rather than the whole of the >AbstractResultSetTests just run some specifc tests. After all, it's the >same autghenticator each time so is running >e.g. results_select_objects_01, 02, 03, 04, ... >actually testing anything more? > >Same for TestRemoteEndpointConnectionWithAuth. > >Or set the HttpClient to stop the HttpOp code creating an HttpClient >each time? > > Andy > > > >> >> >> On 9/25/13 7:29 AM, "Sergio Fernández" <[email protected]> wrote: >> >>> When randomly the build fails, usually it's with this error message: >>> >>> ERROR: Maven JVM terminated unexpectedly with exit code 143 >>> >>> And it looks a known issue in Jenkins: >>> >>> https://issues.jenkins-ci.org/browse/JENKINS-5144 >>> >>> So I'd try to use the solution the propose there (adding the -Xrs flag >>> in global MAVEN_OPTS). Further details about that option at: >>> >>> >>>http://pic.dhe.ibm.com/infocenter/java7sdk/v7r0/index.jsp?topic=%2Fcom.i >>>bm >>> .java.win.70.doc%2Fdiag%2Ftools%2Fdisablingdumpagentswith-xrs.html >>> >>> Personally I never used such option; so let's see how it behaviours... >>> >>> -- >>> Sergio Fernández >> >
