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

grunt test broken #4590

Closed
springuper opened this issue Aug 10, 2015 · 4 comments
Closed

grunt test broken #4590

springuper opened this issue Aug 10, 2015 · 4 comments

Comments

@springuper
Copy link
Contributor

grunt test command is broken after commit 2f07935, the error message is

Running "jest" task
running jest (this may take a while)
Using Jest CLI v0.4.18
 FAIL  src/addons/__tests__/ReactFragment-test.js
TypeError: Cannot read property 'length' of undefined
  at maybeReadMore_ (_stream_readable.js:426:18)
  at /Users/shangchun/Repos/react2/react/node_modules/jest-cli/src/lib/FakeTimers.js:342:7
  at doNTCallback0 (node.js:408:9)
  at process._tickCallback (node.js:337:13)

 FAIL  src/addons/transitions/__tests__/ReactTransitionChildMapping-test.js
Error: Attempted to send a message to the worker before the response from the last message was received! Worker processes can only handle one m
essage at a time.
 FAIL  src/addons/link/__tests__/ReactLinkPropTypes-test.js
TypeError: Cannot read property 'length' of undefined
  at maybeReadMore_ (_stream_readable.js:426:18)
  at /Users/shangchun/Repos/react2/react/node_modules/jest-cli/src/lib/FakeTimers.js:342:7
  at doNTCallback0 (node.js:408:9)
  at process._tickCallback (node.js:337:13)
...
@sairion
Copy link

sairion commented Aug 10, 2015

[edit] It is actually from 8f419c9 and I think $ grunt test is gone.

8f419c9#diff-354f30a63fb0907d4ad57269548329e3L69

@jimfb
Copy link
Contributor

jimfb commented Aug 10, 2015

@springuper AFIK, grunt test still works in latest. Have you done an npm install recently?

@jaredly
Copy link
Contributor

jaredly commented Aug 10, 2015

I've got grunt test breaking for me to on master. fresh node modules, I tried iojs, node 0.12, and node 0.10.
:(

@zpao
Copy link
Member

zpao commented Aug 10, 2015

This is a result of using iojs / node 0.12. We don't currently build with either. We use node 0.10 and npm 2.x. (1.x will have a different issue).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants