www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <br...@apache.org>
Subject Re: Camel.trunk.fulltest.windows - still Failing
Date Tue, 27 Mar 2012 04:46:11 GMT
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

- Brett

On 27/03/2012, at 5:03 AM, Christian Mueller wrote:

> 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 failures.
> The right solution of course is to get the issue with this test fixed. We are working
on this. But until we get this fixed, It would be very helpful for us if someone could kill
the hanging process for us or guide as how we can do it.
> 
> Gavin closed my issue [2] and suggested to ask here for help.
> 
> [1] https://builds.apache.org/view/A-F/view/Camel/job/Camel.trunk.fulltest.windows/311/consoleFull
> [2] https://issues.apache.org/jira/browse/INFRA-4595
> 
> Thanks in advance,
> Christian

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






Mime
View raw message