GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Investigate flaky test test-cluster-worker-forced-exit · Issue #2557 · nodejs/node

Investigate flaky test test-cluster-worker-forced-exit #2557

New issue
Copy link
New issue
Copy link
Closed
Closed
Investigate flaky test test-cluster-worker-forced-exit#2557
Copy link
Labels
armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.

Description

@joaocgreis
joaocgreis
opened on Aug 26, 2015
Issue body actions

Examples of failures:

  • armv7-wheezy

Activity

  1. joaocgreis
    added
    buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.
    testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
    on Aug 26, 2015
  2. brendanashworth
    added
    armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.
    on Aug 26, 2015

  3. Trott commented on Nov 23, 2015

    @Trott
    Trott
    on Nov 23, 2015
    Member
    More actions

    Running this test 9999 times on armv7-wheezy results in no failures:
    https://ci.nodejs.org/job/node-stress-single-test/28/nodes=armv7-wheezy/console

    I propose removing its flaky designation in #3975

    If/when it fails again, we can always add it back.

    Otherwise, maybe something changed in the code or in CI that fixed the issue?

  4. rvagg commented on Nov 23, 2015

    @rvagg
    rvagg
    on Nov 23, 2015
    Member
    More actions

    we did do an upgrade of the slaves on armv7-wheezy at some point, probably between the OP and now, +1 to removing flaky, can you take care of that @Trott?

  5. Trott commented on Nov 23, 2015

    @Trott
    Trott
    on Nov 23, 2015
    Member
    More actions

    @rvagg: Yup. #3975

  6. Trott
    added a commit that references this issue on Nov 24, 2015

    test: remove flaky status for cluster test

    0ff1ba4
  7. Trott
    closed this as completedin 6588422on Nov 24, 2015
  8. Trott
    added 3 commits that reference this issue on Dec 1, 2015

    test: remove flaky status for cluster test

    45e27d1

    test: remove flaky status for cluster test

    950af45

    test: remove flaky status for cluster test

    a863e8d
  9. Trott
    added 2 commits that reference this issue on Dec 17, 2015

    test: remove flaky status for cluster test

    b2f1014

    test: remove flaky status for cluster test

    eb95182
  10. sjarmak
    added a commit that references this issue on Jul 27, 2026

    test: remove flaky status for cluster test

    6588422
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.Issues and PRs related to the ARM architecture.buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.testIssues and PRs related to Node.js core tests and test infrastructure.Issues 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
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.