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

TypeError on Travis CI #8070

Closed
dherault opened this issue Mar 6, 2019 · 7 comments
Closed

TypeError on Travis CI #8070

dherault opened this issue Mar 6, 2019 · 7 comments

Comments

@dherault
Copy link

dherault commented Mar 6, 2019

πŸ› Bug Report

On travis I get the following message:

$ npm test
> piano-keys@1.0.3 test /home/travis/build/dherault/piano-keys
> jest --coverage
 FAIL  ./index.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)
----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |        0 |        0 |        0 |        0 |                   |
----------|----------|----------|----------|----------|-------------------|
Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.763s
Ran all test suites.
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.

To Reproduce

Submit any PR to https://github.com/dherault/piano-keys and open Travis from the PR.

Expected behavior

It should pass all tests on Travis like it does locally.

Link to repl or repo (highly encouraged)

https://github.com/dherault/piano-keys

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: Linux 4.4 Ubuntu 14.04.5 LTS, Trusty Tahr
    CPU: (2) x64 Intel(R) Xeon(R) CPU @ 2.30GHz
  Binaries:
    Node: 11.11.0 - ~/.nvm/versions/node/v11.11.0/bin/node
    Yarn: 1.3.2 - /usr/local/bin/yarn
    npm: 6.7.0 - ~/.nvm/versions/node/v11.11.0/bin/npm
  npmPackages:
    jest: ^24.1.0 => 24.1.0 
@yachtcaptain23
Copy link

Duplicate of #8069

@jeysal
Copy link
Contributor

jeysal commented Mar 6, 2019

This has already been fixed, you can use 24.2.0-alpha.0 to get the fix.

@ragesoss
Copy link

ragesoss commented Mar 7, 2019

@jeysal I tried node 11.11.0, jest 24.2.0-alpha.0 locally on my project, and I still get this error.

@msand
Copy link

msand commented Mar 7, 2019

@ragesoss If you're using yarn then you can add this to your package.json:
msand/react-native-svg-e2e@6c7e597#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R35

  "resolutions": {
    "jest-util": "v24.2.0-alpha.0"
  },

Make sure to use a relatively new yarn (or at least v1)

@msand
Copy link

msand commented Mar 7, 2019

There's also https://www.npmjs.com/package/npm-force-resolutions for npm

@SimenB
Copy link
Member

SimenB commented Mar 7, 2019

Duplicate of #8069 as mentioned

@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

6 participants