Skip to content

jest test runner throws node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message);  #50383

Closed as not planned
Closed as not planned
jest test runner throws node:internal/assert:14 throw new ERR_INTERNAL_ASSERTION(message); #50383
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.netIssues and PRs related to the net subsystem.

Description

@ghost
ghost
opened on Oct 25, 2023

Version

Node.js v20.8.1

Platform

Windows

Subsystem

jest

What steps will reproduce the bug?

image
create a jest unit test for a react functionnal component and run in watch mode

How often does it reproduce? Is there a required condition?

I have like 50 jest unit tests and 10 of them are not even running

What is the expected behavior? Why is that the expected behavior?

test should run the suite
image

What do you see instead?

I don't use another library instead I have a coverage with jest so need this to be fixed

Additional information

No response

Activity

  1. mertcanaltin
    added
    test_runnerIssues and PRs related to the test runner subsystem.
    on Oct 25, 2023

  2. bnoordhuis commented on Oct 25, 2023

    @bnoordhuis
    bnoordhuis
    on Oct 25, 2023
    Member

    @ShogunPanda

  3. ShogunPanda commented on Oct 27, 2023

    @ShogunPanda
    ShogunPanda
    on Oct 27, 2023
    Contributor

    @bnoordhuis Thanks for the heads up.
    I'm narrowing down this bug to a probable conflict in TLS.

    @MaissaTouili Are your jest tests using TLS?

  5. cjihrig
    removed
    test_runnerIssues and PRs related to the test runner subsystem.
    on Nov 16, 2023
  6. tniessen
    added
    netIssues and PRs related to the net subsystem.
    duplicateIssues and PRs that are duplicates of other issues or PRs.
    on Dec 2, 2023

  7. tniessen commented on Dec 2, 2023

    @tniessen
    tniessen
    on Dec 2, 2023
    Member

    I am going to close this as a duplicate of #48763, which is due to #44731. cc @ShogunPanda

  8. tniessen
    closed this as not plannedon Dec 2, 2023

  9. ShogunPanda commented on Dec 22, 2023

    @ShogunPanda
    ShogunPanda
    on Dec 22, 2023
    Contributor

    This should have been fixed in #51045. Once it gets in 21.x or 20.x please let me know if you have additional problems.

  11. joshlarson
    added 7 commits that reference this issue on Feb 14, 2024

    fix: Upgrade node to 21.6.0

    64b427f

    fix: Upgrade node to 20.11.1

    7470718

    fix: Upgrade node to 20.11.1

    6ee0eab

    fix: Upgrade node to 20.11.0

    0eb30eb

    chore/fix: Upgrade node to 20.11.0

    9896916

    chore/fix: Upgrade node to 20.11.0

    081bfda

    chore/fix: Upgrade node to 20.11.0 (#2398)

    63c5999
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

    duplicateIssues and PRs that are duplicates of other issues or PRs.netIssues and PRs related to the net subsystem.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions