Skip to content

parallel/test-domain-error-types is flaky #52034

Closed as not planned
Closed as not planned
parallel/test-domain-error-types is flaky#52034
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@joyeecheung
joyeecheung
opened on Mar 10, 2024
Reason parallel/test-domain-error-types
Type JS_TEST_FAILURE
Failed PR 14 (https://github.com/nodejs/node/pull/51912/, https://github.com/nodejs/node/pull/51977/, https://github.com/nodejs/node/pull/51463/, https://github.com/nodejs/node/pull/51998/, https://github.com/nodejs/node/pull/51999/, https://github.com/nodejs/node/pull/51996/, https://github.com/nodejs/node/pull/52000/, https://github.com/nodejs/node/pull/51880/, https://github.com/nodejs/node/pull/52005/, https://github.com/nodejs/node/pull/51992/, https://github.com/nodejs/node/pull/52016/, https://github.com/nodejs/node/pull/52024/, https://github.com/nodejs/node/pull/51791/, https://github.com/nodejs/node/pull/52010/)
Appeared test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-equinix-ubuntu2004_sharedlibs_container-arm64-6, test-equinix-ubuntu2004_sharedlibs_container-arm64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/57572/
Last CI https://ci.nodejs.org/job/node-test-pull-request/57648/
Example 
not ok 946 parallel/test-domain-error-types
  ---
  duration_ms: 1428.72700
  severity: crashed
  exitcode: -11
  stack: |-
  ...

From nodejs/reliability#807

This started to show up since 03-05 (nodejs/reliability#802) and it seems to be crashing due to segmentation fault on arm debug builds.

Activity

  1. joyeecheung
    added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Mar 10, 2024

  2. lpinca commented on Mar 12, 2024

    @lpinca
    lpinca
    on Mar 12, 2024
    Member

    We might need to revert #51717 and reopen #38063.

  3. github-actions commented on May 22, 2026

    @github-actions
    github-actionsbot
    on May 22, 2026 – with GitHub Actions
    Contributor

    This issue has been marked as stale due to 210 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  4. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on May 22, 2026

  5. github-actions commented on Jun 21, 2026

    @github-actions
    github-actionsbot
    on Jun 21, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

  6. github-actions
    closed this as not plannedon Jun 21, 2026
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

    flaky-testIssues and PRs involving tests that fail intermittently in CI.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions