Hi Gav and Andrew!
Sorry for using the wrong list and txs for taking care (as always)!
LieGrue,
strub
On Monday, 15 September 2014, 18:01, Andrew Bayer
wrote:
>
>
>I think the problem here was
>https://issues.jenkins-ci.org/browse/JENKINS-22641 - Jenkins not
>cleaning up after itself. I'v
[
https://issues.apache.org/jira/browse/BUILDS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer reassigned BUILDS-19:
--
Assignee: Andrew Bayer
> H10 Ubuntu seems to have memory problems
>
[
https://issues.apache.org/jira/browse/BUILDS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134048#comment-14134048
]
Andrew Bayer commented on BUILDS-19:
I think the problem here was https://issues.jenkin
I think the problem here was
https://issues.jenkins-ci.org/browse/JENKINS-22641 - Jenkins not
cleaning up after itself. I've backported the fix to our Jenkins and
restarted it. I'll watch to see how things look.
A.
On Mon, Sep 15, 2014 at 1:53 AM, Gavin McDonald wrote:
> Please direct any build
Hi All,
Just to confirm:-
H1 through to H9 are reserved for Hadoop and related projects (Mapreduce, Yarn
etc…).
Please do not tie your builds to these slaves.
H3 H4 and H9 I found had the 'Ubuntu' label on them so I removed that Label.
H10 and H11 are available for the general ASF projects to
Please direct any build related queries to the builds@ mailing list.
I had a look, 'Jenkins' consists of one master and lots of slaves.
The Master is fine and did not need a restart. The error message indicated
that the slave it was running on was the problem, in this case H10.
I looked and both
