Investigate flaky sequential/test-timers-same-timeout-wrong-list-deleted

[Trott]

Sample failure: https://ci.nodejs.org/job/node-test-binary-windows/3706/RUN_SUBSET=3,VS_VERSION=vcbt2015,label=win10/console

not ok 238 parallel/test-timers-same-timeout-wrong-list-deleted
# 
# assert.js:85
#   throw new assert.AssertionError({
#   ^
# AssertionError: Elapsed time does not include second timer's timeout.
#     at process.<anonymous> (c:\workspace\node-test-binary-windows\RUN_SUBSET\3\VS_VERSION\vcbt2015\label\win10\test\parallel\test-timers-same-timeout-wrong-list-deleted.js:26:10)
#     at emitOne (events.js:101:20)
#     at process.emit (events.js:188:7)
  ---
  duration_ms: 1.128

[Trott]

Might help #8422 if this gets fixed.

@nodejs/testing @Fishrock123 @nodejs/platform-windows

[Fishrock123]

This sounds like an ages old problem where timers on windows fired early, but I thought that got fixed?

cc @misterdjules & @saghul

[saghul]

AFAIK that got fixed :-S

[mscdex]

I just saw this happen on CI on an ubuntu1610-x64 node on the master branch.

not ok 1310 sequential/test-timers-same-timeout-wrong-list-deleted
  ---
  duration_ms: 0.844
  severity: fail
  stack: |-
    
    assert.js:85
      throw new assert.AssertionError({
      ^
    AssertionError: Elapsed time does not include second timer's timeout.
        at process.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1610-x64/test/sequential/test-timers-same-timeout-wrong-list-deleted.js:26:10)
        at emitOne (events.js:101:20)
        at process.emit (events.js:188:7)

[Trott]

Looking at the test, it is inherently flaky and will fail on a machine under load on any operating system. I've removed "Windows" from the title of this issue.

Moving it to sequential probably has helped, but best to fix the test entirely. I'll try to take a look at it later, but if anyone wants to beat me to it, feel free.

[Trott]

Fixed in #10362