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

[Trott]

• 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

[richardlau]

Anyone know what exit code 3221225477 means on Windows?

3221225477 is 0xC0000005 which is STATUS_ACCESS_VIOLATION. Something is attempting to access memory it shouldn't be.

[bzoz]

There is a stress test for this test with this setup from 6 days ago: https://ci.nodejs.org/job/node-stress-single-test/1786/, the test passed. It also does not reproduce on my win10 box.

Possible it was just some random fluke of the CI?

[bzoz]

Nevermind, just saw it failing again: https://ci.nodejs.org/job/node-test-binary-windows/15664/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=3/console

[bzoz]

I've made a stress-test run and it passed: https://ci.nodejs.org/job/node-stress-single-test/1790/, I can't also reproduce this on my win2016 vm.

[Trott]

Might be a hardware or other problem with a specific host.

https://ci.nodejs.org/job/node-test-binary-windows/15664/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=3/console is a failure on test-azure_msft-win2016-x64-1.

https://ci.nodejs.org/job/node-test-binary-windows/15597/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=2/console is also a failure on test-azure_msft-win2016-x64-1.

The successful stress tests are both on test-azure_msft-win2016-x64-6.

[Trott]

I'd like to test the host-specific theory with stress tests, but they don't seem to pick up test-azure_msft-win2016-x64-1. Kicking off multiple stress tests engages test-azure_msft-win2016-x64-6 on the first one and all the others just wait even though test-azure_msft-win2016-x64-1 is idle. Am I doing something wrong? @nodejs/build

Stress test on test-azure_msft-win2016-x64-6 (should pass if theory is correct): https://ci.nodejs.org/job/node-stress-single-test/1791/

[Trott]

Yet another failure and again it's on test-azure_msft-win2016-x64-1: https://ci.nodejs.org/job/node-test-binary-windows/15679/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=0/console

I'm really starting to think that specific host is the problem.

[Trott]

Yet another one on test-azure_msft-win2016-x64-1: https://ci.nodejs.org/job/node-test-binary-windows/15694/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=2/console

This really does seem like there's something wrong with test-azure_msft-win2016-x64-1 specifically. @nodejs/build