Two tests consistently failing on ARM

[mmarchini]

06:05:38 not ok 2486 parallel/test-inspector-multisession-ws
06:05:38   ---
06:05:38   duration_ms: 15.721
06:05:38   severity: fail
06:05:38   exitcode: 1
06:05:38   stack: |-
06:05:38     [test] Connecting to a child Node process
06:05:38     [test] Testing /json/list
06:05:38     [test] Connecting to a child Node process
06:05:38     [test] Testing /json/list
06:05:38     [err] Debugger listening on ws://127.0.0.1:37952/da605906-36d4-4ab7-b55c-738b0eb94832
06:05:38     [err] For help, see: https://nodejs.org/en/docs/inspector
06:05:38     [err] 
06:05:38     [err] Debugger attached.
06:05:38     [err] Debugger attached.
06:05:38     [err] 
06:05:38     [test] Breaking in code and verifying events are fired
06:05:38     Timed out waiting for matching notification (SessionA paused))
06:05:38     1
06:05:38   ...

and

06:09:43 not ok 2799 sequential/test-inspector-break-when-eval
06:09:43   ---
06:09:43   duration_ms: 15.734
06:09:43   severity: fail
06:09:43   exitcode: 1
06:09:43   stack: |-
06:09:43     [test] Connecting to a child Node process
06:09:43     [test] Testing /json/list
06:09:43     [err] Debugger listening on ws://127.0.0.1:37298/a947c724-1b47-4c0c-bd55-4bb6293e65d8
06:09:43     [err] For help, see: https://nodejs.org/en/docs/inspector
06:09:43     [err] 
06:09:43     [test] Setting up a debugger
06:09:43     [err] Debugger attached.
06:09:43     [err] 
06:09:43     [test] Breaking in the code
06:09:43     Timed out waiting for matching notification (break on file:///home/iojs/build/workspace/node-test-commit-arm/nodes/centos7-arm64-gcc6/test/fixtures/inspector-global-function.js:9))
06:09:43     1
06:09:43   ...

I'm seeing it on multiple builds for different commits:

https://ci.nodejs.org/job/node-test-commit-arm/28075/ (#30836)
https://ci.nodejs.org/job/node-test-commit-arm/28076/ (#29987)
https://ci.nodejs.org/job/node-test-commit-arm/28077/ (#30888)

[Trott]

06:05:38 not ok 2486 parallel/test-inspector-multisession-ws
06:05:38   ---
06:05:38   duration_ms: 15.721
06:05:38   severity: fail
06:05:38   exitcode: 1
06:05:38   stack: |-
06:05:38     [test] Connecting to a child Node process
06:05:38     [test] Testing /json/list
06:05:38     [test] Connecting to a child Node process
06:05:38     [test] Testing /json/list
06:05:38     [err] Debugger listening on ws://127.0.0.1:37952/da605906-36d4-4ab7-b55c-738b0eb94832
06:05:38     [err] For help, see: https://nodejs.org/en/docs/inspector
06:05:38     [err] 
06:05:38     [err] Debugger attached.
06:05:38     [err] Debugger attached.
06:05:38     [err] 
06:05:38     [test] Breaking in code and verifying events are fired
06:05:38     Timed out waiting for matching notification (SessionA paused))
06:05:38     1
06:05:38   ...

and

06:09:43 not ok 2799 sequential/test-inspector-break-when-eval
06:09:43   ---
06:09:43   duration_ms: 15.734
06:09:43   severity: fail
06:09:43   exitcode: 1
06:09:43   stack: |-
06:09:43     [test] Connecting to a child Node process
06:09:43     [test] Testing /json/list
06:09:43     [err] Debugger listening on ws://127.0.0.1:37298/a947c724-1b47-4c0c-bd55-4bb6293e65d8
06:09:43     [err] For help, see: https://nodejs.org/en/docs/inspector
06:09:43     [err] 
06:09:43     [test] Setting up a debugger
06:09:43     [err] Debugger attached.
06:09:43     [err] 
06:09:43     [test] Breaking in the code
06:09:43     Timed out waiting for matching notification (break on file:///home/iojs/build/workspace/node-test-commit-arm/nodes/centos7-arm64-gcc6/test/fixtures/inspector-global-function.js:9))
06:09:43     1
06:09:43   ...

I'm seeing it on multiple builds for different commits:

https://ci.nodejs.org/job/node-test-commit-arm/28075/ (#30836)
https://ci.nodejs.org/job/node-test-commit-arm/28076/ (#29987)
https://ci.nodejs.org/job/node-test-commit-arm/28077/ (#30888)

I'm seeing this in the parent job:

stderr: fatal: Unable to create '/home/iojs/build/workspace/node-test-commit-arm/.git/index.lock': File exists.

Wondering if that's cascading down somehow to result in this. I've removed the git.lock file so let's see if that resolves things....

[Trott]

That seems to have fixed it. (Not sure what initially caused it though.)