Actually, I was about to start a new thread on this. We definitely need help from Jenkins admins. I thought it was a problem with us leaving untracked files in the repo, but I found that others elsewhere are getting this sort of problem using Git from Jenkins. Maybe we are the only ones using Git and Jenkins on that Windows slave?
The log we are getting is: 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- Please help, -Alex On 3/21/14 9:38 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: >The builds are broken again this morning. > >I dint think it is a problem with Git or our codebase. > >Let's see if a restart fixes it. If not we can look at other options > >Admins, any ETA on when you can address this issue? > >Thanks, >Om >On Mar 20, 2014 11:47 AM, "Alex Harui" <aha...@adobe.com> wrote: > >> I don't know if a restart is required because I got a clean sdk build by >> cleaning the sdk's git working copy before starting the jenkins build. >> I'm wondering if there is some upgrade to git that is making it >>sensitive >> to the SDK build leaving untracked files. >> >> It would be nice if at least one person on the Flex team could have file >> read/write/delete privileges on the Windows slave so cleaning up would >>be >> easier. >> >> -Alex >> >> On 3/20/14 11:40 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: >> >> >Hi, >> > >> >The following builds are stuck: >> > >> >flex-sdk >> >flex-sdk_pixelbender >> >flex-sdk_release >> >flex-falcon >> > >> >due to similar sounding git related errors. >> > >> >Ex. >> > >> >FATAL <http://stacktrace.jenkins-ci.org/search?query=FATAL>: Could not >> >checkout null with start point >> >b303d9eff21d508b954c7c578e4a61ff53919e18 >> >... >> >Caused by: hudson.plugins.git.GitException: Command "git checkout -f >> >b303d9eff21d508b954c7c578e4a61ff53919e18" returned status code 1: >> >stdout: Process leaked file descriptors. See >> >>>http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build >> >for more information >> > >> >Perhaps windows1 needs a restart? >> > >> >Thanks, >> >Om >> > >> > >> >On Wed, Mar 19, 2014 at 10:41 AM, OmPrakash Muppirala >> ><bigosma...@gmail.com>wrote: >> > >> >> Admins, while you are there, please take a look at the builds that >>have >> >> been failing on Windows1 since last night [1]. >> >> >> >> Looks like a git process is hung somewhere. You will need to >>manually >> >> delete the file for the builds to continue to work: >> >> >> >> f:/hudson/hudson-slave/workspace/flex-sdk/.git/index.lock >> >> >> >> Thanks, >> >> Om >> >> >> >> [1] https://builds.apache.org/job/flex-sdk/677/console >> >> >> >> >> >> On Wed, Mar 19, 2014 at 4:31 AM, Erik de Bruin <e...@ixsoftware.nl> >> >>wrote: >> >> >> >>> > >> >>> > Windows1 is back online and taking jobs >> >>> > >> >>> >> >>> Thank you! >> >>> >> >>> If you have a little (more) time, can you look at the other two >>issues >> >>> with >> >>> 'windows1' (listed below) as well, please? >> >>> >> >>> >> >>> > > > Can some admin with a few minutes time on their hands please >> >>>look at >> >>> > > these >> >>> > > > two issues? >> >>> > > > >> >>> > > > This one: >> >>> > > > >> >>> > > > The file " >> >>> > > >> >> >>> > > >> >>> > >> >>> >> >>> >> https://builds.apache.org/job/flex-falcon/ws/compiler\generated\dist\sdk >> >>>\lib\compiler.jar >> >>> > > < >> >>> > > >> >>> > >> >>> >> >>> >> https://builds.apache.org/job/flex-falcon/ws/compiler/generated/dist/sdk >> >>>/lib/compiler.jar >> >>> > > >" >> >>> > > >> cannot be deleted by Jenkins "because it's in use by another >> >>> process". >> >>> > > The >> >>> > > >> inability to delete this file is blocking the rest of the >>build. >> >>> > > >> >> >>> > > >> Can you please manually delete that file? >> >>> > > >> >> >>> > > > >> >>> > > > And this one: >> >>> > > > >> >>> > > > >> >>> > > >> I was running a build on the Windows 1 slave that launches >>the >> >>> Flash >> >>> > > >>> Player to run a test. It looks like the Player launched but >> >>>never >> >>> > > >>> exited. >> >>> > > >>> Subsequent runs indicate that the SWF it was trying to run >>is >> >>> still >> >>> > > >>> open, >> >>> > > >>> probably by the player. Can someone see if that's true and >> >>>kill >> >>> the >> >>> > > >>> Flash >> >>> > > >>> Player process? Is there a way we can kill that process in >>the >> >>> > future. >> >>> > > >>> I >> >>> > > >>> have a feeling it will do this again until we figure out >>what >> >>>the >> >>> > cause >> >>> > > >>> is. >> >>> > >> >>> >> >>> Thank you! >> >>> >> >>> EdB >> >>> >> >>> >> >>> >> >>> -- >> >>> Ix Multimedia Software >> >>> >> >>> Jan Luykenstraat 27 >> >>> 3521 VB Utrecht >> >>> >> >>> T. 06-51952295 >> >>> I. www.ixsoftware.nl >> >>> >> >> >> >> >> >>
