You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Martin Grigorov (Reopened) (JIRA)" <ji...@apache.org> on 2012/01/27 09:34:39 UTC
[jira] [Reopened] (INFRA-4360) Wicket BuildBot jobs times out
[ https://issues.apache.org/jira/browse/INFRA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reopened INFRA-4360:
------------------------------------
Unfortunately it still doesn't work.
There are 6 pending builds and the slave machine (hemera_ubuntu) is offline.
See http://ci.apache.org/builders/wicket-master
> Wicket BuildBot jobs times out
> -------------------------------
>
> Key: INFRA-4360
> URL: https://issues.apache.org/jira/browse/INFRA-4360
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Buildbot
> Reporter: Martin Grigorov
> Assignee: Tony Stevenson
>
> Several build jobs for wicket-master and wicket-branch-1.5.x failed with :
> command timed out: 1200 seconds without output, attempting to kill
> process killed by signal 9
> program finished with exit code -1
> elapsedTime=1200.004318
> Here are few such builds:
> http://ci.apache.org/builders/wicket-branch-1.5.x/builds/48
> http://ci.apache.org/builders/wicket-master/builds/119/steps/compile/logs/stdio
> http://ci.apache.org/builders/wicket-master/builds/118/steps/compile/logs/stdio failed with JVM crach. I suspect this is the main reason.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira