I did notice a similar OOM on the weekend, before spi-fly went in. I
increased the maven heap but I guess that wasn't the underlying issue.
Holly
On 6 Sep 2012, at 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>
