investigate flaky sequential/test-inspector-stop-profile-after-done

  • Version: 10.0.0-pre (master)
  • Platform: win2016 vs2017
  • Subsystem: inspector test

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

not ok 535 sequential/test-inspector-stop-profile-after-done
  ---
  duration_ms: 6.574
  severity: fail
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:55287/eddeff2f-6cfe-4edd-8a6d-d17133dee77a
    [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:28:10)
        at process._tickCallback (internal/process/next_tick.js:114:7)
      generatedMessage: true,
      name: 'AssertionError [ERR_ASSERTION]',
      code: 'ERR_ASSERTION',
      actual: 0,
      expected: 3221225477,
      operator: 'strictEqual' }
    1
  ...

Anyone know what exit code 3221225477 means on Windows? ("actual" and "expected" are reversed above. I'll submit a PR to fix the test.)

@nodejs/platform-windows @nodejs/testing @nodejs/v8-inspector