www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BUILDS-42) Jenkins to GIT fetch errors (Jena)
Date Wed, 17 Dec 2014 16:15:13 GMT

     [ https://issues.apache.org/jira/browse/BUILDS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andy Seaborne resolved BUILDS-42.
---------------------------------
    Resolution: Done

Wiping the projects workspaces seems to have made the builds work again. (maybe something
else got fixed at the same time).

> Jenkins to GIT fetch errors (Jena)
> ----------------------------------
>
>                 Key: BUILDS-42
>                 URL: https://issues.apache.org/jira/browse/BUILDS-42
>             Project: Infra Build Platform
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Andy Seaborne
>
> This is different to BUILDS-33 where the error was a return code of 143 and it's 128
here. This is not a 10 min timeout - it takes a few seconds to appear.
> Seen on Ubuntu2 and Ubuntu4, both manually requested builds and automatically triggered
by timer.
> https://builds.apache.org/job/Jena_Development_Test/1662/console
> https://builds.apache.org/job//Jena_Development_Deploy/799/console
> {noformat}
> Started by user andy
> Building remotely on ubuntu-4 (docker Ubuntu ubuntu4 ubuntu) in workspace /home/jenkins/jenkins-slave/workspace/Jena_Development_Test
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url git://git.apache.org/jena.git # timeout=10
> Fetching upstream changes from git://git.apache.org/jena.git
>  > git --version # timeout=10
>  > git fetch --tags --progress git://git.apache.org/jena.git +refs/heads/*:refs/remotes/origin/*
> FATAL: Failed to fetch from git://git.apache.org/jena.git
> hudson.plugins.git.GitException: Failed to fetch from git://git.apache.org/jena.git
> 	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:647)
> 	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:889)
> 	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:914)
> 	at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
> 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615)
> 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
> 	at hudson.model.Run.execute(Run.java:1706)
> 	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
> 	at hudson.model.ResourceController.execute(ResourceController.java:88)
> 	at hudson.model.Executor.run(Executor.java:232)
> Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress git://git.apache.org/jena.git
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
> stdout: 
> stderr: fatal: read error: Connection reset by peer
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message