Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node 11.11.0 Prevents Jest 23.6.0 from Running Suites #8103

Closed
Aghassi opened this issue Mar 11, 2019 · 3 comments
Closed

Node 11.11.0 Prevents Jest 23.6.0 from Running Suites #8103

Aghassi opened this issue Mar 11, 2019 · 3 comments

Comments

@Aghassi
Copy link
Contributor

Aghassi commented Mar 11, 2019

πŸ› Bug Report

All my suites fail using Node 11.11.0 with the following

 FAIL  tests/lib/utils/getRenderer.test.js
  ● Test suite failed to run

    TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>'

      at _default (node_modules/jest-util/build/createProcessObject.js:85:34)

To Reproduce

Steps to reproduce the behavior:

  1. Clone https://github.com/Aghassi/oclif-jest-demo-failure
  2. Set the version of jest (and related packages) in package json to 23.6.0
  3. yarn
  4. yarn jest

Expected behavior

All tests should pass, but in fact all tests fail

@Aghassi Aghassi changed the title Node 11.11.0 Prevents Jest 23.6.0 from Running Node 11.11.0 Prevents Jest 23.6.0 from Running Suites Mar 11, 2019
@thymikee
Copy link
Collaborator

Duplicate of #8069

Either use Jest 24 (recommended) or wait for Node fixing the regression.

@Aghassi
Copy link
Contributor Author

Aghassi commented Mar 11, 2019

@thymikee Thanks for the fast response. I'm still waiting on #7923 to resolve my issue. Until then, I can't upgrade to 24.x.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants