Open ljay79 opened 5 years ago
Sorry completely missed this. I have not had this issue at all. What version of node are you using and is the issue still occuring?
Still happening, all details see above.
Ah sorry - missed that too! :) This must be an issue with Jest / Node on your machine. I'm sure its a bug but not one I can fix with the code in this Repo (or probably one I can fix at all!)
We can try updating Jest to the latest version. Currently its locked on 23.6.x in package.json I'll do that in a quick branch and give you a pull request. If you still have the issue then we should submit a report to the Jest team.
Yeah i believe its due to my environment ubuntu under windows 10 WSL. I have similar behavior when working on other projects with docker when the project processes a lot of files.
I will see, how far i can deal with it by executing unit tests one by one instead of all at once.
using npm test
will run all tests - does that have the same issue?
npx jest --coverage
runs all tests and generates a coverage report to help you see gaps where the unit tests may need improving. I only run that before I make a pull request and that's not essential
Same with npm test
. Fails almost always with a different error every time. Always some kind of cannot find module or similar things from node_modules directory.
Running
npx jest --coverage
fails randomly.Running above command multiple times without any changes to source or environment, brings different results every time.
Any idea why?
Lastest develop branch with merged changes from your authmode change. Running Ubuntu for Windows 10 WSL
Output: