Skip to content

test-debug-signal-cluster fails on centos7 #340

Closed
aliscco/alisco-node
#198
Closed
test-debug-signal-cluster fails on centos7#340
aliscco/alisco-node
#198
Labels
testIssues and PRs related to Node.js core tests and test infrastructure.

Description

@rvagg
rvagg
opened on Jan 13, 2015

I think this is intermittent but I've seen it a couple of times already in the same way, only on CentOS 7 (i.e. EL7), e.g. https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/nodes=iojs-centos7-64/71/console

=== release test-debug-signal-cluster ===
Path: parallel/test-debug-signal-cluster
> all workers are running
> Starting debugger agent.
> Debugger listening on port 12343
> Starting debugger agent.
> Debugger listening on port 12345
got pids [12731,12737,12743]

assert.js:100
  throw new assert.AssertionError({
        ^
AssertionError: 4 == 6
    at assertOutputLines (/home/iojs/build/workspace/iojs+any-pr+multi/nodes/iojs-centos7-64/test/parallel/test-debug-signal-cluster.js:80:10)
    at onNoMoreLines [as _onTimeout] (/home/iojs/build/workspace/iojs+any-pr+multi/nodes/iojs-centos7-64/test/parallel/test-debug-signal-cluster.js:48:3)
    at Timer.listOnTimeout (timers.js:90:15)
Command: out/Release/iojs /home/iojs/build/workspace/iojs+any-pr+multi/nodes/iojs-centos7-64/test/parallel/test-debug-signal-cluster.js

Activity

  1. bnoordhuis commented on Jan 13, 2015

    @bnoordhuis
    bnoordhuis
    on Jan 13, 2015
    Member

    I've been looking at this test for some time now. The problem is that the feature it tests is inherently timing sensitive (sending signals to start the debugger) but I'm not quite ready to delete it outright. Will keep you posted.

  2. piscisaureus commented on Jan 16, 2015

    @piscisaureus
    piscisaureus
    on Jan 16, 2015
    Contributor

    nodejs/node-v0.x-archive@58fcc65
    nodejs/node-v0.x-archive@e9df9a0

    Both seem good to land to me.

  3. rvagg commented on Jan 17, 2015

    @rvagg
    rvagg
    on Jan 17, 2015
    MemberAuthor

    👍

  4. brendanashworth
    added
    testIssues and PRs related to Node.js core tests and test infrastructure.
    on Feb 12, 2015

  5. Fishrock123 commented on Mar 23, 2015

    @Fishrock123
    Fishrock123
    on Mar 23, 2015
    Contributor

    Do we still need those two commits? I haven't seen a red centos CI anywhere recently..

  6. bnoordhuis commented on Mar 23, 2015

    @bnoordhuis
    bnoordhuis
    on Mar 23, 2015
    Member

    This may have been fixed by 4dd22b9 or 11c1bae (although the second commit predates this issue by a day.) I'll close the issue and reopen if necessary.

  7. bnoordhuis
    closed this as completedon Mar 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    testIssues and PRs related to Node.js core tests and test infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions