www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pascal Schumacher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11238) Groovy pull request builds on build.apache.org often fail with "malloc(): memory corruption:"
Date Sun, 14 Feb 2016 10:33:18 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146484#comment-15146484

Pascal Schumacher commented on INFRA-11238:

In the last few days every pull build seems to fail with either:

*** Error in `/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.6/bin/java': free():
invalid next size (fast): 0x00007f3f1c9ed420 ***


*** Error in `/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.6/bin/java': malloc():
memory corruption: 0x00007fd610ade1f0 ***


> Groovy pull request builds on build.apache.org often fail with "malloc(): memory corruption:"
> ---------------------------------------------------------------------------------------------
>                 Key: INFRA-11238
>                 URL: https://issues.apache.org/jira/browse/INFRA-11238
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Pascal Schumacher
> We use builds.apache.org to test pull request, but sadly these frequently fail with:
> *** Error in `/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.6/bin/java':
malloc(): memory corruption: 0x00007f1b7cb418c0 ***
> e.g.:
> https://builds.apache.org/job/Groovy%20Github%20PRs/241/console
> https://builds.apache.org/job/Groovy%20Github%20PRs/238/console
> https://builds.apache.org/job/Groovy%20Github%20PRs/238/console
> this seems like an issue on build.apache.org, because I have never seen this failure
nether on your teamcity buildserver nor locally.
> This is frustrating for your contributors because because there appears to be an issue
with their contribution, when it really is an infrastructure issue.
> It would be nice if you could look into this.
> Thank you very much!

This message was sent by Atlassian JIRA

View raw message