On Wed, Apr 11, 2012 at 9:29 PM, Christian Müller
wrote:
> Thanks Brett, but it didn't worked. It failed again for the same reason:
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean
> (default-clean) on proj
t; [2]
> >
> https://builds.apache.org/view/A-F/view/Camel/job/Camel.trunk.fulltest.windows/328/console
> >
> > Thanks in advance,
> > Christian
> >
> > -- Forwarded message --
> > From: Christian Müller
> > Date: Wed, Mar 28, 2012 at 12
age --
> From: Christian Müller
> Date: Wed, Mar 28, 2012 at 12:07 AM
> Subject: Re: Camel.trunk.fulltest.windows - still Failing
> To: d...@camel.apache.org
> Cc: builds@apache.org
>
>
> Thanks Brett for this hint. I opened a JIRA for Camel [1] and started
> workin
://builds.apache.org/view/A-F/view/Camel/job/Camel.trunk.fulltest.windows/328/console
Thanks in advance,
Christian
-- Forwarded message --
From: Christian Müller
Date: Wed, Mar 28, 2012 at 12:07 AM
Subject: Re: Camel.trunk.fulltest.windows - still Failing
To: d...@camel.apache.org
Cc: builds
Thanks Brett for this hint. I opened a JIRA for Camel [1] and started
working on it.
[1] https://issues.apache.org/jira/browse/CAMEL-5124
Best,
Christian
On Tue, Mar 27, 2012 at 6:46 AM, Brett Porter wrote:
> Jenkins was wedged on there anyway, so I rebooted the VM. You should be
> good to go
Jenkins was wedged on there anyway, so I rebooted the VM. You should be good to
go again.
I'm not aware of any easy way to be able to kill that test from Jenkins, but
perhaps you could try this:
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkedProcessTimeoutInSeconds
-
We have again and again a problem to get our Windows build running after one of
our tests fails [1]. It looks like the test took to long. The process itself is
still existing and prevents Jenkins in the next build to delete the
camel-core-XXX.jar artifact. This is the reason for all next build f
