Thank you Emily. I did pull the changes and rebuilt.
Indeed, I didn't have any application itest failures!
However, I did hit test failures in:
- Blueprint itests - QuiesceBlueprintTest (perhaps one of your references?)
- JPA itests - QuiesceJPATest (another quiesce test :-( )
- Blog itests - JdbcBlogSampleWithEbaTest
All of the failures look somewhat similar - a service timeout. But I
also see bundle resolution errors due to some package uses conflicts,
IllegalStateExceptions for an unregistered service, and
InvocationTargetExceptions in the output. I think the blog failure may
have only had the InvocationTargetException without the others referenced.
Joe
On 9/17/10 5:30 PM, Emily Jiang wrote:
I have fixed the application itests intermittent failures. After you have
pulled the latest changes into your local repository, you should not see
application itests failures any more. If it is not the case, please let me
know. The fix does not fix the quiesce test failures though:(.
Has someone started looking at the intermittent quiesce test failures?
Thanks
Emily
From: Joe Bohn<[email protected]>
To: [email protected]
Date: 16/09/2010 18:11
Subject: Re: building Apache Aries trunk from the top level pom
On 9/16/10 12:58 PM, Alasdair Nottingham wrote:
On 16 September 2010 01:45, Holly Cummins<[email protected]> wrote:
I wonder if running with a bigger heap would help?
That is plausible. I don't have these issues and I have to run with a
non-default heap size or the build fails with OOM errors on my mac.
Perhaps 512m is big enough not to see these errors.
My MAVEN_OPTS="-XX:MaxPermSize=512m -Xms1024m -Xmx1024m"
I'm also using mac ... which I was wondering for a time if it was
related to the mac jdk - but it seems that is not the case given others
are seeing similar issues on other environments.
---
Joe
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
--
Joe
