Skip to content

Investigate flaky test-cluster-worker-init on Raspberry Pi 1 #8700

Description

@Trott

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

not ok 24 parallel/test-cluster-worker-init
# 
# assert.js:85
#   throw new assert.AssertionError({
#   ^
# AssertionError: message not received
#     at Timeout._onTimeout (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-cluster-worker-init.js:14:5)
#     at Timer.unrefdHandle (timers.js:460:14)

/cc @cjihrig

Activity

  1. added
    clusterIssues and PRs related to the cluster subsystem.
    testIssues and PRs related to Node.js core tests and test infrastructure.
    armIssues and PRs related to the ARM architecture.
    on Sep 21, 2016
  2. imyller commented on Sep 21, 2016

    @imyller
    Member

    Possibly resolved. PR coming soon.

    Stress test CI with pi1 looks promising:
    https://ci.nodejs.org/job/node-stress-single-test-pi1-binary/label=pi1-raspbian-wheezy/14/

  3. imyller commented on Sep 22, 2016

    @imyller
    Member

    @Trott IMHO it was a good idea to open an issue for investigating this one. 👍

    I know there are more testing issues causing arm-fanned CI group failures. Maybe you could open "investigate" issues for those as well. More people can jump in to sort them out.

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

    armIssues and PRs related to the ARM architecture.clusterIssues and PRs related to the cluster subsystem.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