Investigate flaky test-regress-GH-4027 on pi1

[targos]

https://ci.nodejs.org/job/node-test-binary-arm/3993/RUN_SUBSET=3,label=pi1-raspbian-wheezy/tapTestReport/test.tap-173/

not ok 173 sequential/test-regress-GH-4027
# /home/iojs/build/workspace/node-test-binary-arm/test/common.js:55
# throw e;
# ^
# 
# Error: EBUSY: resource busy or locked, unlink '/home/iojs/build/workspace/node-test-binary-arm/test/tmp.0/.nfs00000000001c3d7700000033'
# at Object.fs.unlinkSync (fs.js:1014:18)
# at rimrafSync (/home/iojs/build/workspace/node-test-binary-arm/test/common.js:48:10)
# at fs.readdirSync.forEach (/home/iojs/build/workspace/node-test-binary-arm/test/common.js:71:11)
# at Array.forEach (native)
# at rmdirSync (/home/iojs/build/workspace/node-test-binary-arm/test/common.js:68:30)
# at rimrafSync (/home/iojs/build/workspace/node-test-binary-arm/test/common.js:46:7)
# at Object.exports.refreshTmpDir (/home/iojs/build/workspace/node-test-binary-arm/test/common.js:82:3)
# at Object.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/sequential/test-regress-GH-4027.js:7:8)
# at Module._compile (module.js:560:32)
# at Object.Module._extensions..js (module.js:569:10)

@nodejs/testing

[Trott]

This looks like an NFS issue that @nodejs/build has been investigating, I think, on the Raspberry Pi devices. /cc @rvagg

[targos]

Maybe. I opened this issue and #8760 because the error consistently happens with the same tests. Most recent examples:
https://ci.nodejs.org/job/node-test-binary-arm/3997/RUN_SUBSET=3,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3996/RUN_SUBSET=1,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3996/RUN_SUBSET=3,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3992/RUN_SUBSET=3,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3991/RUN_SUBSET=3,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3990/RUN_SUBSET=3,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3989/RUN_SUBSET=3,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3989/RUN_SUBSET=1,label=pi1-raspbian-wheezy/tapTestReport/
https://ci.nodejs.org/job/node-test-binary-arm/3989/RUN_SUBSET=2,label=pi1-raspbian-wheezy/tapTestReport/

[targos]

I'm happy to close as a duplicate if the NFS issue is already being tracked somewhere.

[Trott]

I don't think it's being tracked, at least not in this repo. I think it's fine to leave this issue open until it's resolved. If someone else sees the same thing, at least they will see this issue and know that people are aware of it.