jest: Jest fails all the time due to "Failed to cache transform results" on Windows

This is happening to me as well on Windows 7 with jest@21.1.0, --runInBand resolves it but that makes it run significantly slower. There should be an actual solution to this.

i’ll create a new ticket

This is still an issue. I have my jest version set to “x” (meaning: always latest and greatest), my CI server does a git clean -fdx and npm install before build (and there is no package-lock.json in the project) and I still see stuff like this:

  jest: failed to read cache file: D:/phoenix/src/.jest-cache/jest-transform-cache-f691fb298581eda406946da746f68cf3-791c88db313af6e97cd5a90a918831b1/e6/order_e6d4e287214676f983806bccb2f628dc
    Failure message: ENOENT: no such file or directory, open 'D:/phoenix/src/.jest-cache/jest-transform-cache-f691fb298581eda406946da746f68cf3-791c88db313af6e97cd5a90a918831b1/e6/order_e6d4e287214676f983806bccb2f628dc'
      at readCacheFile (node_modules/jest-runtime/build/script_transformer.js:563:60)

(cache file went away?)

or this:

FAIL tests/components/tracking/tracking.vue.spec.ts
  â—� Test suite failed to run
    jest: failed to read cache file: D:/phoenix/src/.jest-cache/jest-transform-cache-f691fb298581eda406946da746f68cf3-791c88db313af6e97cd5a90a918831b1/f0/auto-completion-session_f0091c924a4ebc768da80b8fc8735194
    Failure message: EPERM: operation not permitted, open 'D:/phoenix/src/.jest-cache/jest-transform-cache-f691fb298581eda406946da746f68cf3-791c88db313af6e97cd5a90a918831b1/f0/auto-completion-session_f0091c924a4ebc768da80b8fc8735194'
      at readCacheFile (node_modules/jest-runtime/build/script_transformer.js:563:60)

(cache file still being generated?)

The caching mechanism needs to cater for this and other issues – if it can’t read the file it expects to, simply regenerate it with a new id. Which is worse: a small slowdown because a race condition made a cache file go away, or an entire build failing sporadically because of cache misses?

Reinstall node_modules and it should be fine

Hello. Short note.

For me problems with “Failed to cache transform results” stops when I added --runInBand flag. (Win7)

Same issue here. Fixed it by updating all Jest dependencies to latest versions:

- "babel-jest": "23.0.0",
- "eslint-plugin-jest": "21.15.2",
- "jest": "23.0.0",
- "jest-cli": "23.0.0",
+ "babel-jest": "23.4.0",
+ "eslint-plugin-jest": "21.17.0",
+ "jest": "23.4.1",
+ "jest-cli": "23.4.1",

I think we need to reopen this issue, I can still see the same error. --runInBand will resolve it but it is really too slow.

I’m running into this issue on Windows 7 with Jest 24.0.0.

Getting this issue on node v8.9.4 and npm v5.6.0 in typescript. Got it to work by running jest with -i switch.

Likely dup of https://github.com/facebook/jest/issues/4444

--runInBand works for me but i dont want to run in band…

windows 10 node 8.4.0 npm 5.3.0 jest 21.0.2 babel-jest 21.0.2

I haven’t had time to upgrade Node and test with the new Jest, but after the quite long time of the problem happening often, now suddenly it doesn’t anymore. So I’ll close for now and reopen with more details if it starts happening again.