Investigate flaky test-regress-GH-4027 on Windows

Version: 9.0.0-pre
Platform: win2012r2,vs2015
Subsystem: test

https://ci.nodejs.org/job/node-test-binary-windows/9310/RUN_SUBSET=1,VS_VERSION=vs2015,label=win2012r2/console

not ok 387 sequential/test-regress-GH-4027
  ---
  duration_ms: 5.421
  severity: fail
  stack: |-
    assert.js:60
      throw new errors.AssertionError({
      ^
    
    AssertionError [ERR_ASSERTION]: 0 === 1
        at StatWatcher.<anonymous> (c:\workspace\node-test-binary-windows\RUN_SUBSET\1\VS_VERSION\vs2015\label\win2012r2\test\sequential\test-regress-GH-4027.js:35:10)
        at StatWatcher.<anonymous> (c:\workspace\node-test-binary-windows\RUN_SUBSET\1\VS_VERSION\vs2015\label\win2012r2\test\common\index.js:517:15)
        at emitTwo (events.js:125:13)
        at StatWatcher.emit (events.js:213:7)
        at StatWatcher._handle.onchange (fs.js:1454:10)

/cc @nodejs/testing @nodejs/platform-windows

Perhaps a race condition triggered by system load, which probably explains why it's in sequential and not parallel in the first place?