investigate flaky known_issues/test-vm-timeout-escape-nexttick

[Trott]

https://ci.nodejs.org/job/node-test-commit-smartos/21423/nodes=smartos16-64/console

21:00:05 not ok 2313 known_issues/test-vm-timeout-escape-nexttick
21:00:05   ---
21:00:05   duration_ms: 0.525
21:00:05   severity: fail
21:00:05   stack: |-
21:00:05   ...

@jasnell

[Trott]

Fails reliably, it seems on Raspberry Pi devices.

https://ci.nodejs.org/job/node-test-binary-arm/3931/RUN_SUBSET=0,label=pi1-docker/console

01:56:21 not ok 313 known_issues/test-vm-timeout-escape-nexttick # TODO : Fix flaky test
01:56:21   ---
01:56:21   duration_ms: 2.609
01:56:21   severity: flaky
01:56:21   stack: |-
01:56:21   ...

https://ci.nodejs.org/job/node-test-binary-arm/3931/RUN_SUBSET=0,label=pi2-docker/console

00:12:31 not ok 313 known_issues/test-vm-timeout-escape-nexttick # TODO : Fix flaky test
00:12:31   ---
00:12:31   duration_ms: 1.235
00:12:31   severity: flaky
00:12:31   stack: |-
00:12:31   ...

https://ci.nodejs.org/job/node-test-binary-arm/3931/RUN_SUBSET=0,label=pi3-docker/console

00:09:09 not ok 313 known_issues/test-vm-timeout-escape-nexttick # TODO : Fix flaky test
00:09:09   ---
00:09:09   duration_ms: 0.927
00:09:09   severity: flaky
00:09:09   stack: |-
00:09:09   ...

[Trott]

@nodejs/vm

[refack]

Still there testing https://github.com/nodejs/node/commits/8920d5d896b3f9b5df47b02e779ab49136cca085 which includes d8e06b2:

11:06:52 not ok 313 known_issues/test-vm-timeout-escape-nexttick
11:06:52   ---
11:06:52   duration_ms: 1.235
11:06:52   severity: fail
11:06:52   stack: |-
11:06:52   ...

https://ci.nodejs.org/job/node-test-commit-arm-fanned/4141/
https://ci.nodejs.org/job/node-test-binary-arm/3949/RUN_SUBSET=0,label=pi2-docker/console
https://ci.nodejs.org/computer/test-requireio_svincent-debian9-armv7l_pi2-1