Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to create '/home/iojs/build/workspace/node-test-binary-arm/.git/index.lock': File exists. #1048

Closed
bnoordhuis opened this issue Dec 19, 2017 · 5 comments

Comments

@bnoordhuis
Copy link
Member

I've seen this a few times in the past days now:

+ ps -ef
+ grep '\[node\] <defunct>'
+ awk '{print $2}'
+ xargs -rl kill
+ rm -f ****
+ git checkout -f refs/remotes/jenkins_tmp
fatal: Unable to create '/home/iojs/build/workspace/node-test-binary-arm/.git/index.lock': File exists.

Another git process seems to be running in this repository, e.g.
an editor opened by 'git commit'. Please make sure all processes
are terminated then try again. If it still fails, a git process
may have crashed in this repository earlier:
remove the file manually to continue.
Build step 'Execute shell' marked build as failure

https://ci.nodejs.org/job/node-test-binary-arm/12698/RUN_SUBSET=2,label=pi1-raspbian-wheezy/consoleText

@Trott
Copy link
Member

Trott commented Dec 19, 2017

I'm removing stale .git/index.lock on the Raspberry Pi devices as I find them, but I don't know the cause.

@Trott
Copy link
Member

Trott commented Dec 19, 2017

@rvagg

@Trott
Copy link
Member

Trott commented Dec 19, 2017

Also Ref: #951

@Trott
Copy link
Member

Trott commented Dec 19, 2017

I've removed all the stale index.lock files I could find. and CI is heading towards green again. https://ci.nodejs.org/job/node-test-binary-arm/12703/

I'm going to close this as the immediate issue is resolved, but the root cause still needs to be found, and that is being tracked in #951.

@Trott Trott closed this as completed Dec 19, 2017
@rvagg
Copy link
Member

rvagg commented Dec 19, 2017

Sorry @Trott, was asleep at the time this hit. I did restart the nfs server and all of the pi's yesterday so I guess it's related to that, glad it's fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants