investigate flaky test-fs-utimes in CI on Pi2

[Trott]

Originally posted by @mhdawson in #36591 (comment)

Failed in CI as well: https://ci.nodejs.org/job/node-test-binary-arm-12+/lastCompletedBuild/RUN_SUBSET=0,label=pi2-docker/testReport/(root)/test/parallel_test_fs_utimes/ although with different error:

ode:assert:399
    throw err;
    ^

AssertionError [ERR_ASSERTION]: FAILED: expect_errno [Arguments] {
  '0': 'futimesSync',
  '1': 22,
  '2': AssertionError [ERR_ASSERTION]: FAILED: expect_ok [Arguments] {
    '0': 'futimesSync',
    '1': 22,
    '2': undefined,
    '3': '123456',
    '4': -1
  }
       check_mtime: 2.3949999809265137
      at expect_ok (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:64:3)
      at syncTests (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:142:7)
      at /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:120:11
      at /home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:377:15
      at FSReqCallback.oncomplete (node:fs:184:23) {
    generatedMessage: false,
    code: 'ERR_ASSERTION',
    actual: undefined,
    expected: true,
    operator: '=='
  },
  '3': 'ENOSYS'
}
    at expect_errno (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:56:3)
    at syncTests (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:144:7)
    at /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:120:11
    at /home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:377:15
    at FSReqCallback.oncomplete (node:fs:184:23) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: false,
  expected: true,
  operator: '=='
}

[Trott]

CI failure again:

https://ci.nodejs.org/job/node-test-binary-arm-12+/9681/RUN_SUBSET=3,label=pi2-docker/console

00:39:33 not ok 229 parallel/test-fs-utimes
00:39:33   ---
00:39:33   duration_ms: 4.757
00:39:33   severity: fail
00:39:33   exitcode: 1
00:39:33   stack: |-
00:39:33     node:assert:402
00:39:33         throw err;
00:39:33         ^
00:39:33     
00:39:33     AssertionError [ERR_ASSERTION]: FAILED: expect_ok [Arguments] {
00:39:33       '0': 'futimes',
00:39:33       '1': 22,
00:39:33       '2': null,
00:39:33       '3': '123456',
00:39:33       '4': -1
00:39:33     }
00:39:33          check_mtime: 2.0460000038146973
00:39:33         at expect_ok (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:64:3)
00:39:33         at /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:118:11
00:39:33         at /home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:376:15
00:39:33         at FSReqCallback.oncomplete (node:fs:190:23) {
00:39:33       generatedMessage: false,
00:39:33       code: 'ERR_ASSERTION',
00:39:33       actual: null,
00:39:33       expected: true,
00:39:33       operator: '=='
00:39:33     }
00:39:33   ...

[anonrig]

This is still flaky https://ci.nodejs.org/job/node-test-commit-plinux/55201/nodes=rhel8-ppc64le/testReport/junit/(root)/parallel/test_fs_utimes/

[aduh95]

Cannot reproduce on macOS

$ tools/test.py --repeat 9999 test/parallel/test-fs-utimes.js -t 9 
[07:05|% 100|+ 9999|-   0]: Done                  

All tests passed.

[jasnell]

I was able to reproduce on ubuntu by testing a theory... I ran a couple other parallel processes to stress the host and then ran the test. The flake here may be caused by too much running in parallel. I suggest we try moving the test to sequential and see if that helps.