I reported the problem and it seems to be fixed now.
https://issues.apache.org/jira/browse/INFRA-3383

Christian


Am 21.01.2011 17:04, schrieb Christian Schneider:
The latest failures could be an infrastructure problem (Too many open files).
Should we report this to infra or is it internal to our build?

Christian


-----Ursprüngliche Nachricht-----
Von: Hadrian Zbarcea [mailto:hzbar...@gmail.com]
Gesendet: Freitag, 21. Januar 2011 16:57
An: dev@camel.apache.org
Betreff: Re: Preparing for Camel 2.6 release

I would like to have at least one clean build in hudson before the release. 
Other than that we're good to go. Looks like the latest build didn't go to well 
[1]. I am looking into it. As soon as we have something green I'll start 
building the release.

Hadrian

[1] 
https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/lastBuild/testReport/

On Jan 21, 2011, at 10:41 AM, Claus Ibsen wrote:

Hi

Dan Kulp have confirmed that CXF 2.3.2 has been voted and released.

I have just commited the updates to the camel trunk code to upgrade to
CXF 2.3.2.
We should be good to go for a release.
We have been testing with 2.3.2-SNAPSHOT for a week so the camel-cxf
should work well with the upgrade.


Hadrian take it away when you have the time.


On Fri, Jan 21, 2011 at 10:32 AM, Claus Ibsen<claus.ib...@gmail.com>  wrote:
Hi

Okay Camel 2.6 seems good now. Just fixed a few tests failures
reported on CI servers, often due they are much slower than our local
fast laptops.

CXF 2.3.2 is about to hit the streets so we should be good to go.

So please refrain from committing to trunk, unless its a CI unit test fix :).
New features or improvements should be postponed for Camel 2.7.

Lets keep the activity on the trunk low so the CI servers have good
chance to battle test it.

Willem will commit the upgrade to CXF 2.3.2 which in fact may already
be in central maven repo.


On Tue, Jan 18, 2011 at 1:07 PM, Claus Ibsen<claus.ib...@gmail.com>  wrote:
Hi

I have created a ticket to upgrade to CXF 2.3.2
https://issues.apache.org/jira/browse/CAMEL-3553

The CXF vote is in progress
http://cxf.547215.n5.nabble.com/VOTE-Apache-CXF-2-3-2-td3345633.html

And the Camel source code trunk is testing against a 2.3.2-SNAPSHOT.
So we use that to catch any early issues.

Better would have been to add the staging repo for the 2.3.2 and use
that :)


We should focus on fixing any last minute bugs and ensures the
release has successful tests.
https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/





--
Claus Ibsen
-----------------
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/ Author of Camel in Action:
http://www.manning.com/ibsen/



--
Claus Ibsen
-----------------
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/



--
Claus Ibsen
-----------------
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/


--
----
http://www.liquid-reality.de

Reply via email to