Due to nodejs/node#1215 my tests fail in Node v4.0.0

[chrisportela]

https://github.com/facebook/jest/blob/master/src/TestRunner.js#L357-L372

Jest uses path.dirname with undefined variables

I commented out the catch in lines 511-540 and got this error:

Failed with unexpected error.
/Users/cp/Code/frontend/src/node_modules/jest-cli/src/jest.js:191
      throw error;
      ^

TypeError: Path must be a string. Received undefined
  at assertPath (path.js:8:11)
  at Object.posix.relative (path.js:494:3)
  at DefaultTestReporter.onTestResult (/Users/cp/Code/frontend/src/node_modules/jest-cli/src/DefaultTestReporter.js:44:12)
  at DefaultTestReporter.IstanbulTestReporter.onTestResult (/Users/cp/Code/frontend/src/node_modules/jest-cli/src/IstanbulTestReporter.js:16:46)
  at onTestResult (/Users/cp/Code/frontend/src/node_modules/jest-cli/src/TestRunner.js:439:39)
  at /Users/cp/Code/frontend/src/node_modules/jest-cli/src/TestRunner.js:510:13
  at process._tickCallback (node.js:356:9)

I'm going to continue trying to figure out a solution because this breaks all my tests in node v4.0.0 right now.

[chrisportela]

Actually, seems it might be an issue with DefaultTestReporter line 44 where it uses path.relative

For some reason my testResult.testFilePath is undefined. testResult is a string error.

[cpojer]

I think there might be a SyntaxError in your code somewhere that is being wrongly recorded. I'll take a look shortly.

[cpojer]

Well, the bigger issue in jest is that there is a promise exception that is still getting swallowed somewhere...

[cpojer]

Can you run the test that failed alone, without workers? jest MyTest.js or jest --runInBand should do that and give you an appropriate error message while I fix this bug.

[chrisportela]

I think this is an non-issue. I deleted jest-cli from my node_modules and npm installed again and it runs again. My tests are failing very strangely, but at least they are running and report failing

[cpojer]

Thanks! There might have been some caching issues from the upgrade. We should probably wipe away the cache dir if the jest version doesn't match up.

[github-actions]

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.