CI linter job failure due to infrastructure issue?

[vsemozhetbyt]

We have several linter job failures in various PRs with the similar cause:

https://ci.nodejs.org/job/node-test-linter/17685/console

Is some manual cleaning needed on the job's machine?

[vsemozhetbyt]

It seems fixed somehow. I am not sure if this is a normal situation. I've seen this already last days several times. Feel free to close if this is OK.

[gibfahn]

Maybe fixed by #19746?

[vsemozhetbyt]

FWIW, cc @nodejs/build @nodejs/linting

[gibfahn]

Actually I think this is a separate issue, the job was failing on a particular machine (test-rackspace-freebsd10-x64-1).

I went onto the machine and deleted the index.lock file it was complaining about, and it seems to be okay now.

https://ci.nodejs.org/job/node-test-linter/17689/

If it happens again you can raise an issue in nodejs/build.

Alternatively in cases like this you can just delete the workspace on that executor and rerun the job. If you click the Workspace button it gives you the option to Wipe Out Current Workspace. You need to make sure it's the workspace on the machine that has the issue. That will delete the git lock file (and fix workspace messed up errors in general). It should always be okay to delete a workspace.

https://ci.nodejs.org/job/node-test-linter/ws/

So for example you see a failing job, make a note of the machine:

Go to the top-level job and click the workspace button:

Then make sure it is the workspace on the right machine (if not just run builds until it is):

Then click the Wipe out current workspace button and it'll clean the workspace. Then rerun the job (making sure it runs on the right executor)

[vsemozhetbyt]

Thank you!