Re: Build failed in Jenkins: Cassandra-quick #162

Unfortunately Jenkins tries to run all the Cassandra branches at once and gets port conflicts like this. Maybe we should restrict Jenkins to either current-stable or to trunk. On Wed, Dec 7, 2011 at 10:21 AM, Ted Crossman wrote: > Hi all, > > I was just wondering if this mailing list only sees t

Re: Build failed in Jenkins: Cassandra-quick #162

Hi all, I was just wondering if this mailing list only sees the failures, while successful builds are happening and the list is not being alerted to them? Seems kind of pointless to have the e-mail being sent if no one does anything about them :) Just curious, tedo On 12/7/11 7:57 AM, Ap

Build failed in Jenkins: Cassandra-quick #162

See Changes: [jbellis] update CHANGES -- [...truncated 1694 lines...] [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.833 sec [junit] [junit] Testsuite: org.apache.cassa