www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7488) flex-sdk (and other) Jenkins builds failing
Date Wed, 26 Mar 2014 20:36:18 GMT

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

Alex Harui commented on INFRA-7488:
-----------------------------------

We are still stuck.  Can we get the versions of Jenkins and Git on the Windows slaves so we
can try it on other machines?  We have Jenkins working on one developer's machines with the
following versions:
Jenkins: 1.549
git: 2.0.1
git-client: 1.6.2



> flex-sdk (and other) Jenkins builds failing
> -------------------------------------------
>
>                 Key: INFRA-7488
>                 URL: https://issues.apache.org/jira/browse/INFRA-7488
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: Windows1 Slave
>            Reporter: Alex Harui
>            Assignee: Gavin
>
> flex-sdk and flex-sdk-release builds are failing due to apparent git configuration issue.
> Sample log:
> Started by timer
> Building remotely on windows1 (Windows) in workspace
> <https://builds.apache.org/job/flex-sdk/ws/>
> Fetching changes from the remote Git repository
> Fetching upstream changes from
> https://git-wip-us.apache.org/repos/asf/flex-sdk.git
> Checking out Revision ce9e3b00db03171e79353e5f1799f56f997a4362
> (origin/develop)
> ERROR: Timeout after 10 minutes
> FATAL: Could not checkout null with start point
> ce9e3b00db03171e79353e5f1799f56f997a4362
> hudson.plugins.git.GitException: Could not checkout null with start point
> ce9e3b00db03171e79353e5f1799f56f997a4362
> 	at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.
> java:1309)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocation
> Handler.java:299)
> 	at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHan
> dler.java:280)
> 	at
> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHan
> dler.java:239)
> 	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> 	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> 	at hudson.remoting.Request$2.run(Request.java:328)
> 	at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorServ
> ice.java:72)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> 	at java.util.concurrent.FutureTask.run(Unknown Source)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> 	at hudson.remoting.Engine$1$1.run(Engine.java:63)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: hudson.plugins.git.GitException: Command "git checkout -f
> ce9e3b00db03171e79353e5f1799f56f997a4362" returned status code 1:
> stdout: Process leaked file descriptors. See
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build
> for more information
> I looked up "Jenkins Git leaked file descriptors".  Some articles point to
> the way git is launched [1]  and this one by Jukka recommends this post
> [2].
> [1] https://issues.jenkins-ci.org/browse/JENKINS-17894
> [2] https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message