Yes, neither spy-fly nor samples were apparently built. But would you have any idea of that from the build messages we received? There's nothing about subsystems either. I happened to take a look "just in case" :)
John > > Re: Jenkins build is unstable: Aries #1675 > > FWIW I don't think the addition of the spi-fly module can have > anything to do with it as it is built/tested after subsystems, so the > build hasn't even hit that yet... > > David > > On 6 September 2012 14:37, John W Ross <[email protected]> wrote: > > > > I see that the subsystem itests have gone nuts starting with build 1674. > > The execution time is absurdly high and they're followed by an OOM error > > when the test harness tries to archive the test results. There have been no > > changes to subsystems since build 1673. The only changes were the addition > > of spi-fly to the build and a couple of changes to the openejb-extender > > poms. There's no clear connection but it seems like some change to the test > > environment must have been the catalyst. I'd like to be able to look at the > > individual test results but they're not available on Jenkins, presumably > > because of the OOM. Does anyone know if it's possible to browse the file > > system on the build machine directly? > > > > The only other thing I can think of to do is a local build with a fresh svn > > checkout and m2 repository to see if it can be duplicated. > > > > John > > > >> > >> Subject > >> > >> Jenkins build is unstable: Aries #1675 > >> > >> See <https://builds.apache.org/job/Aries/1675/changes> > >> >
