I think the reason we get the multiple messages about stable and unstable is that different tests are failing. So the *sub-build* for a particular test went stable, while a different sub-build started failing. I'm not sure if that level of detail in the emails is helpful or not - what do people think?
What I don't understand, though, is why we're all of a sudden seeing so much instability, particularly in the non-snapshot build. Most of the itests in the "Aries" build are testing the released versions of bundles (which is why we have the "AriesWithSnapshotDependencies" build), so I wouldn't expect to see many failures beyond fairly simple compile failures and unit test ones. I did wonder if there's some interference somehow between the two builds, but they *should* be using different local maven repos. To add to the confusion, our builds stopped running for a while between Wednesday and Thursday, so a bunch of commits all got bundled together into a big build on Thursday. I'll have a dig and see if I can understand what's going on, especially since I'd like to have a stable build before I do the next round of releases, too. Holly On Fri, Aug 31, 2012 at 12:41 PM, John W Ross <[email protected]> wrote: > > I'm a little confused about these Jenkins build messages. My email chain > first indicates it went unstable, then went back to stable, and finally > that it's still unstable. ARIES-910 would not have had an impact. ARIES-912 > might have, but I don't see the connection. The one test failure I see is > from org.apache.aries.application.runtime.isolated.itests. The build works > fine locally with a fresh SVN checkout and m2 repository. Any thoughts? > > java.lang.NullPointerException > at > org.apache.aries.application.runtime.framework.management.SharedFrameworkPreResolveHook.collectFakeResources > (SharedFrameworkPreResolveHook.java:161) > at > Proxy52d21b5c_e2a6_4fd8_b621_974d360a2f8a.collectFakeResources(Unknown > Source) > at > org.apache.aries.application.deployment.management.impl.DeploymentManifestManagerImpl.generateDeployedBundles > (DeploymentManifestManagerImpl.java:214) > at > org.apache.aries.application.deployment.management.impl.DeploymentManifestManagerImpl.generateDeploymentManifest > (DeploymentManifestManagerImpl.java:166) > at > Proxy48256bcb_be2e_49b4_94fe_8675f1b7e010.generateDeploymentManifest > (Unknown Source) > at > org.apache.aries.application.management.impl.AriesApplicationManagerImpl.resolve > (AriesApplicationManagerImpl.java:286) > at > org.apache.aries.application.management.impl.AriesApplicationManagerImpl.install > (AriesApplicationManagerImpl.java:303) > at > org.apache.aries.application.runtime.itests.IsolatedRuntimeTest.testAppWithFragment > (IsolatedRuntimeTest.java:209) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.injectContextAndInvoke > (CallableTestMethodImpl.java:143) > at > org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.call > (CallableTestMethodImpl.java:105) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl.remoteCall > (RemoteBundleContextImpl.java:80) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at sun.rmi.server.UnicastServerRef.dispatch > (UnicastServerRef.java:305) > at sun.rmi.transport.Transport$1.run(Transport.java:159) > at java.security.AccessController.doPrivileged(Native Method) > at > sun.rmi.transport.Transport.serviceCall(Transport.java:155) > at sun.rmi.transport.tcp.TCPTransport.handleMessages > (TCPTransport.java:535) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0 > (TCPTransport.java:790) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run > (TCPTransport.java:649) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask > (ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run > (ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > > Apache Jenkins Server <[email protected]> wrote on 08/31/2012 > 05:30:18 AM: > >> Apache Jenkins Server <[email protected]> >> 08/31/2012 05:30 AM >> >> Please respond to >> [email protected] >> >> To >> >> [email protected], [email protected], John W Ross/ >> Atlanta/IBM@IBMUS, [email protected], [email protected], >> >> cc >> >> Subject >> >> Jenkins build is still unstable: Aries #1651 >> >> See <https://builds.apache.org/job/Aries/changes> >>
