cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aristedes Maniatis <...@maniatis.org>
Subject Re: Jenkins; Build Failure?
Date Fri, 15 Aug 2014 01:22:04 GMT
On 15/08/2014 11:03am, Andrew Lindesay wrote:
> Hello;
> 
> I see there's a CI build failure with my change noted!
> 
> ---
> Changes:
> 
> [apl] CAY-1935 EJBQL; Handling Collection as Parameter in IN Expression
> ---
> 
> I tried to login to the Jenkins instance to see what the error is, but it is not allowing
me access.  Is there a means by which I can find out the cause of this failure?
> 
> The stack trace in the email looks more like a build-issue than an actual automated test
failure.


You don't need to log in to see the full log from the build.

https://builds.apache.org/job/cayenne-master/cayenneTestConnection=derby,jdk=JDK%201.7%20%28latest%29,label=Ubuntu/14/consoleFull


INFO: failed JNDI lookup of DataSource location 'jdbc/TestDS'
Aug 14, 2014 9:06:30 PM org.apache.cayenne.log.CommonsJdbcEventLogger logConnectFailure
INFO: *** Connecting: FAILURE.
javax.naming.NameNotFoundException: Name [jdbc/TestDS] not bound; 0 bindings: []
	at org.springframework.mock.jndi.SimpleNamingContext.lookup(SimpleNamingContext.java:134)
	at javax.naming.InitialContext.lookup(InitialContext.java:411)
	at org.apache.cayenne.configuration.server.JNDIDataSourceFactory.lookupViaJNDI(JNDIDataSourceFactory.java:80)
	at org.apache.cayenne.configuration.server.JNDIDataSourceFactory.getDataSource(JNDIDataSourceFactory.java:51)
	at org.apache.cayenne.configuration.server.JNDIDataSourceFactoryTest.testGetDataSource_NameNotBound(JNDIDataSourceFactoryTest.java:97)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at junit.framework.TestCase.runTest(TestCase.java:176)
	at junit.framework.TestCase.runBare(TestCase.java:141)
	at junit.framework.TestResult$1.protect(TestResult.java:122)
	at junit.framework.TestResult.runProtected(TestResult.java:142)
	at junit.framework.TestResult.run(TestResult.java:125)
	at junit.framework.TestCase.run(TestCase.java:129)
	at junit.framework.TestSuite.runTest(TestSuite.java:255)
	at junit.framework.TestSuite.run(TestSuite.java:250)
	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102)
	at org.apache.maven.surefire.Surefire.run(Surefire.java:180)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)


And yes, Jenkins will quite often randomly fail. But from a cursory look I cannot see what
caused this failure.

My rule of thumb is to let it build again and only then investigate a failure if it is still
happening.


Ari



-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Mime
View raw message