flake: `sequential/test-inspector-stop-profile-after-done`

[refack]

• Version: master
• Platform: Windows
• Subsystem: inspector,test

https://ci.nodejs.org/job/node-test-binary-windows/12525/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=3/console

not ok 506 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 124.922
  severity: fail
  stack: |-
    timeout
  ...

Refs: #14507

[refack]

/cc @nodejs/v8-inspector

[Trott]

Again today: https://ci.nodejs.org/job/node-test-binary-windows/12549/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=3/console

not ok 506 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 128.785
  severity: fail
  stack: |-
    timeout
``

[Trott]

Now on Raspberry Pi too:

https://ci.nodejs.org/job/node-test-binary-arm/RUN_SUBSET=6,label=pi1-raspbian-wheezy/11617/console:

not ok 278 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 360.77
  severity: fail
  stack: |-
    timeout

Looks like this resulted in the device failing to build multiple times subsequently. @rvagg indicated it was due to a zombie process. So maybe it came about due to this test failure?

[Trott]

Another windows one. Looks like it only ever happens on win2016 vs2017 hosts in CI.

https://ci.nodejs.org/job/node-test-binary-windows/12634/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=3/console

not ok 507 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 123.544
  severity: fail
  stack: |-
    timeout

[refack]

In the reports I see 3/3 VS2017 fails, so this might be related to #15558

[refack]

See if we can repro (single test x 100 repeats)
win2012r2-mp-vs2015 - https://ci.nodejs.org/job/node-stress-single-test/1548/
win2012r2-mp-vs2017 - https://ci.nodejs.org/job/node-stress-single-test/1549/

[Trott]

Today on Raspberry Pi:

https://ci.nodejs.org/job/node-test-binary-arm/11870/RUN_SUBSET=4,label=pi1-raspbian-wheezy/console

20:26:43 not ok 282 sequential/test-inspector-stop-profile-after-done
20:26:43   ---
20:26:43   duration_ms: 360.111
20:26:43   severity: fail
20:26:43   stack: |-
20:26:43     timeout

[mmarchini]

Today on Raspbery Pi again:

https://ci.nodejs.org/job/node-test-binary-arm/11987/RUN_SUBSET=3,label=pi1-raspbian-wheezy/console

11:57:59 not ok 283 sequential/test-inspector-stop-profile-after-done
11:57:59   ---
11:57:59   duration_ms: 360.66
11:57:59   severity: fail
11:57:59   stack: |-
11:57:59     timeout

[Trott]

WIndows again but this time an assertion failure rather than a timeout:

https://ci.nodejs.org/job/node-test-binary-windows/13307/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=2/console

not ok 518 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 0.680
  severity: fail
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:61080/4b6bfeec-65aa-4129-b2c3-2cd3c829c1dc
    [err] For help see https://nodejs.org/en/docs/inspector
    [err] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [out] {}
    [out] 
    [err] Debugger attached.
    [err] Waiting for the debugger to disconnect...
    [err] 
    { AssertionError [ERR_ASSERTION]: 0 strictEqual 3221225477
        at runTests (c:\workspace\node-test-binary-windows\test\sequential\test-inspector-stop-profile-after-done.js:26:10)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:165:7)
      generatedMessage: true,
      name: 'AssertionError [ERR_ASSERTION]',
      code: 'ERR_ASSERTION',
      actual: 0,
      expected: 3221225477,
      operator: 'strictEqual' }
    1

[Trott]

Back to a timeout on Windows:

https://ci.nodejs.org/job/node-test-binary-windows/13846/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=1/console

not ok 524 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 127.567
  severity: fail
  stack: |-
    timeout
  ...

[Trott]

It does appear that this test takes an unusually large amount of time to run:

ok 524 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 35.635
  ...

In comparison, the test takes less than a second to run on (for example) our CentOS 7 test machine:

ok 2029 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 0.620

That's quite a difference....

[Trott]

If we could get the output of the test when it times out, that would let us know how far along it got. (One reason I'm not super-excited about the tendency to remove console.log()/console.error() statements from tests.)

@refack Any chance you can run the test locally and get an idea where it seems to do al its waiting?