Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AIX: parallel/test-cluster-inspector-debug-brk intermittent failures #11830

Closed
mhdawson opened this issue Mar 13, 2017 · 4 comments · May be fixed by adamlaska/node#11, adamlaska/node#12, adamlaska/node#14, adamlaska/node#15 or adamlaska/node#16
Labels
aix Issues and PRs related to the AIX platform. cluster Issues and PRs related to the cluster subsystem. inspector Issues and PRs related to the V8 inspector protocol test Issues and PRs related to the tests.

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 13, 2017

  • Version: master
  • Platform: AIX
  • Subsystem: debug

Failed in recent run on test-osuosl-aix61-ppc64_be-1:

https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix61-ppc64/4371/

not ok 145 parallel/test-cluster-inspector-debug-brk
  ---
  duration_ms: 0.946
  severity: fail
  stack: |-
    Debugger listening on port 12346.
    Warning: This is an experimental feature and could change at any time.
    To start debugging, open the following URL in Chrome:
        chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:12346/96c43f40-8e51-4b52-93f9-18337191abd6
    Debugger listening on port 12347.
    Warning: This is an experimental feature and could change at any time.
    To start debugging, open the following URL in Chrome:
        chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:12347/bcacbed6-1c15-4913-ab4f-2e5acb7d5a1a
    Debugger listening on port 12348.
    Warning: This is an experimental feature and could change at any time.
    To start debugging, open the following URL in Chrome:
        chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:12348/588c12b9-cc5a-48cf-a638-213a320a7fe7
    Debugger listening on port 12349.
    Warning: This is an experimental feature and could change at any time.
    To start debugging, open the following URL in Chrome:
        chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:12349/18ce9a5a-0ffb-4bfb-9587-b313cc4e008c
    Debugger listening on port 12350.
    Warning: This is an experimental feature and could change at any time.
    To start debugging, open the following URL in Chrome:
        chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:12350/06ed0f67-96e8-4f61-b388-fd77d3d7fafc
    
    assert.js:81
      throw new assert.AssertionError({
      ^
    AssertionError: 0 === null
        at Worker.worker.on.common.mustCall (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/parallel/test-cluster-inspector-debug-brk.js:19:14)
        at Worker.<anonymous> (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/common.js:473:15)
        at emitTwo (events.js:127:13)
        at Worker.emit (events.js:215:7)
        at ChildProcess.worker.process.once (internal/cluster/master.js:188:12)
        at Object.onceWrapper (events.js:314:19)
        at emitTwo (events.js:127:13)
        at ChildProcess.emit (events.js:215:7)
        at Process.ChildProcess._handle.onexit (internal/child_process.js:208:12)
  ...
@mscdex mscdex added aix Issues and PRs related to the AIX platform. cluster Issues and PRs related to the cluster subsystem. inspector Issues and PRs related to the V8 inspector protocol test Issues and PRs related to the tests. labels Mar 13, 2017
@mhdawson
Copy link
Member Author

Don't see any stray processes on the machine that might have been related.

@mhdawson
Copy link
Member Author

@santigimeno
Copy link
Member

@mhdawson the PR containing that test hasn't landed yet. See: #11471

@mhdawson
Copy link
Member Author

@santigimeno thanks, I was through off by the Changes listing which just said '1. fix linting error' but I now remember that was likely part of a set of changes being tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment