[Gluster-devel] netbsd smoke failure

[Susant Palai]

Thanks Michael :)

----- Original Message -----
From: "Michael Scherer" <mscherer at redhat.com>
To: "Susant Palai" <spalai at redhat.com>
Cc: "Gluster Devel" <gluster-devel at gluster.org>
Sent: Friday, 29 April, 2016 8:54:50 PM
Subject: Re: [Gluster-devel] netbsd smoke failure

Le vendredi 29 avril 2016 à 10:05 -0400, Susant Palai a écrit :
> Hi All,
>   On many of my patches the following error is seen from netbsd smoke test.
> 
> Triggered by Gerrit: http://review.gluster.org/13993
> Building remotely on netbsd0.cloud.gluster.org (netbsd_build) in workspace /home/jenkins/root/workspace/netbsd6-smoke
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url git://review.gluster.org/glusterfs.git # timeout=10
> ERROR: Error fetching remote repo 'origin'
> hudson.plugins.git.GitException: Failed to fetch from git://review.gluster.org/glusterfs.git
> 	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810)
> 	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066)
> 	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097)
> 	at hudson.scm.SCM.checkout(SCM.java:485)
> 	at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
> 	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
> 	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
> 	at hudson.model.Run.execute(Run.java:1738)
> 	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> 	at hudson.model.ResourceController.execute(ResourceController.java:98)
> 	at hudson.model.Executor.run(Executor.java:410)
> Caused by: hudson.plugins.git.GitException: Command "git config remote.origin.url git://review.gluster.org/glusterfs.git" returned status code 255:
> stdout: 
> stderr: error: could not lock config file .git/config: File exists
> 
> 
> 
> Please let me know how this can be resolved.

So as I didn't add access, I ran a groovy script to add my key as root.
Then i did reboot the server (since some old process were running), and
then removed the file causing trouble ( .git/config.lock in the repo ).

I will reenable the builder back soon.
-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS