Re: Bad Jenkins Slave?

On Sun, Feb 22, 2015 at 12:50 AM, Norbert Thiebaud <nthiebaud@gmail.com> wrote:
> On Sat, Feb 21, 2015 at 9:17 PM, Ashod Nakashian <ashnakash@gmail.com> wrote:
> > TB57[1] was idle when it failed to mkdirs during build #873 [2]. Error
> > below.
> >
> >
> > Anyone able and inclined enough to take a look?
>
> Thanks.
> Should be fixed now.

Thanks Norbert.

Same slave, different error (build 903):

Building remotely on tb57 (Windows Gerrit) in workspace
C:\cygwin/home/tdf/lode/jenkins\workspace\lo_gerrit_master\Gerrit\Gerrit\Platform\Windows
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://gerrit.libreoffice.org/core # timeout=10
Fetching upstream changes from git://gerrit.libreoffice.org/core
> git --version # timeout=10
> git fetch --tags --progress git://gerrit.libreoffice.org/core
refs/changes/*:refs/changes/* # timeout=90
Checking out Revision c843b6101bb676a30057493de1de3012469554e4
(refs/changes/97/14597/1)
> git config core.sparsecheckout # timeout=10
> git checkout -f c843b6101bb676a30057493de1de3012469554e4 # timeout=30
java.io.IOException: Could not checkout c843b6101bb676a30057493de1de3012469554e4
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:995)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1265)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitLockFailedException: Could not lock
repository. Please try again
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1634)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
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 java.lang.Thread.run(Unknown Source)
at ......remote call to tb57(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy38.execute(Unknown Source)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:992)
... 9 more
Caused by: hudson.plugins.git.GitException: Command "git checkout -f
c843b6101bb676a30057493de1de3012469554e4" returned status code 128:
stdout:
stderr: fatal: Unable to create
'/home/tdf/lode/jenkins/workspace/lo_gerrit_master/Gerrit/Gerrit/Platform/Windows/.git/index.lock':
File exists.



> PS: Windows 2012 somehow ended-up with a 'ghost' directory that no-one
> could delete not even Admin ( Windows these days is so secure than
> even Administrator does not have the permission to delete files....
> yeah that is the symptom: 'Permission denied' whatever you try to do
> with that Directory...)
> Solution: Standard Microsoft Support Technique: Reboot. Hard to
> imagine that some people are running this crap on 'production' system
> :-/

*sigh*