Re: [Resteasy-users] Sloppy Pull Requests == Broken Builds

2013-10-24 Thread Matthias Wessendorf
On Thu, Oct 24, 2013 at 4:31 PM, Bill Burke wrote: > There may be permgen/memory issues with the CI build too. I thought I > had cleaned this up a few weeks ago by upgrading the > maven-compiler-plugin, but this seems to have regressed and builds are > requiring gigabytes of ram to pass. I have

Re: [Resteasy-users] Sloppy Pull Requests == Broken Builds

2013-10-24 Thread Bill Burke
There may be permgen/memory issues with the CI build too. I thought I had cleaned this up a few weeks ago by upgrading the maven-compiler-plugin, but this seems to have regressed and builds are requiring gigabytes of ram to pass. I haven't had time to track this down yet. On 10/24/2013 4:52

Re: [Resteasy-users] Sloppy Pull Requests == Broken Builds

2013-10-24 Thread Bill Burke
I don't see this problem. This is a Garbage Collector test, so it is possible that the CI build machine will have intermittent failures for this test. On 10/24/2013 4:52 AM, Matthias Wessendorf wrote: > did a rebase and the new build now failed here: > > Failed tests: > testConnectionCleanup

Re: [Resteasy-users] Sloppy Pull Requests == Broken Builds

2013-10-24 Thread Matthias Wessendorf
did a rebase and the new build now failed here: Failed tests: testConnectionCleanupErrorNoGC(org.jboss.resteasy.test.client.ApacheHttpClient4Test): expected:<30> but was:<20> https://travis-ci.org/matzew/Resteasy/builds/12973751 -M On Thu, Oct 24, 2013 at 10:25 AM, Anthony Whitford wrote:

Re: [Resteasy-users] Sloppy Pull Requests == Broken Builds

2013-10-24 Thread Anthony Whitford
Thumbs up! The particular build problem (unable to download dependency) is resolved now as the invalid repository declaration has been fixed. Note that the pom.xml files don't mention a SNAPSHOT version, so running a build the way things are right now, every time it rebuilds version 3.0.5.Fina