Sure, but the tests we are talking about only failing rarely. It's not so
easy to spot the issue and to make sure it's fixed.

Best,

Christian
-----------------

Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

https://www.linkedin.com/pub/christian-mueller/11/551/642

On Mon, Nov 10, 2014 at 8:05 AM, Babak Vahdat <babak.vah...@swissonline.ch>
wrote:

> Hi
>
> Could we maybe then at least raise a ticket for all those failing tests we
> spot while trying to prepare the release. Then the community could look
> into
> and fix them either for the same RC or the upcoming releases, as I guess
> more people look into the JIRA tickets compared to the Jenkins build
> results
> by the day X.
>
> Babak
>
> Christian Mueller wrote
> > Hi,
> >
> > I do NOT think this is possible at present. It would be great if it's
> > possible, but it doesn't work yet...
> > For Camel 2.12.5, I tried it 7 times with the test enabled - and it
> failed
> > each time (but with different test). At present, we have to many test
> > which
> > are failing from time to time.
> >
> > Regarding the 2.13.3 release: As a PMC, we may did not the best job when
> > we
> > vote +1 for a release which is constantly failing on Jenkins at this
> time.
> > However, I will check this in the next releases...
> >
> > Best,
> > Christian
> > -----------------
> >
> > Software Integration Specialist
> >
> > Apache Member
> > V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> > Apache Incubator PMC Member
> >
> > https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Camel-2-12-5-and-2-13-3-releases-tp5757263p5758809.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>

Reply via email to