The Apache Jenkins build system has built Camel.trunk.notest (build #1450)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1450/
to view the results.
I reopened the issue. Waiting for some action from INFRA...
Best,
Christian
On Sat, Jan 28, 2012 at 11:21 AM, Babak Vahdat
wrote:
> Hi
>
> We're still suffering from the ed up Windows, Jenkins running on it:
>
> https://builds.apache.org/job/Camel.trunk.fulltest.windows/
>
> I put some comme
On Sat, Jan 28, 2012 at 2:44 PM, Hadrian Zbarcea wrote:
> I will look into the reason for failure. On the fact that it does the same
> you are wrong. You totally missed the nature of the test. Previously the
> trigger was not firing at the right times after a restart. I am working on
> fixes and i
I will look into the reason for failure. On the fact that it does the
same you are wrong. You totally missed the nature of the test.
Previously the trigger was not firing at the right times after a
restart. I am working on fixes and improvements in the quartz component
now. I will add some deta
Hi
We're still suffering from the ed up Windows, Jenkins running on it:
https://builds.apache.org/job/Camel.trunk.fulltest.windows/
I put some comments into:
https://issues.apache.org/jira/browse/INFRA-4272
Which to my understanding should be reopened! @Christian would you please do
that?
The test keeps failing occasionally on CI servers.
The test does the same.
Restart the route, and checks that when the route is stopped, that
quartz, does not emit new messages.
On Fri, Jan 27, 2012 at 9:11 PM, Hadrian Zbarcea wrote:
> I have no idea what prompted this change, but it removed i
