test staleness-sync-test failing on arm32

[rickysarraf]

One of the tests in basic.js, staleness sync test, fails on amr32 hardware. This is seen on our setup with the following version:

Distribuiton: Debian Stretch
lockfile: 1.0.4-1

What I've noticed is that the Debian maintainer replaced the requirement for the touch module with the native calls to fs module. I doubt if something that simple would be the cause of the problem but I've anyways also asked the Debian Maintainer to help provide some information on why that change was made.

Currently, the test fails with the following error:

[  253s]     # Subtest: staleness test
[  253s]         ok 1 - expect falsey value
[  253s]         1..1
[  253s]     ok 7 - staleness test # time=12.937ms
[  253s]     
[  253s]     # Subtest: staleness sync test
[  253s]         ok 1 - expect falsey value
[  253s]         not ok 2 - EEXIST: file already exists, open 'stale-lock'
[  253s]           ---
[  253s]           stack: |
[  253s]             Object.exports.lockSync (lockfile.js:277:17)
[  253s]             Test.<anonymous> (test/basic.js:161:12)
[  253s]           at:
[  253s]             line: 439
[  253s]             column: 3
[  253s]             file: fs.js
[  253s]             function: Object.openSync
[  253s]           errno: -17
[  253s]           syscall: open
[  253s]           code: EEXIST
[  253s]           path: stale-lock
[  253s]           test: staleness sync test
[  253s]           ...
[  253s]         
[  253s]         1..2
[  253s]         # failed 1 of 2 tests
[  253s]     not ok 8 - staleness sync test # time=75.656ms
[  253s]     
[  253s]     # Subtest: retries
[  253s]         ok 1 - should be equal
[  253s]         1..1
[  253s]     ok 9 - retries # time=8.388ms
[  253s]     
[  253s]     # Subtest: retryWait
[  253s]         ok 1 - should be equal
[  253s]         1..1
[  253s]     ok 10 - retryWait # time=404.541ms