jest: sporadic "failed to cache transform results" error
See original GitHub issueI’m observing sporadic errorneous behaviour when running tests. janosimas reported the same issue here: #175
Observation: For the last 4 occurrences, the error message is about file
Not true - sporadic on any test file.random.alea.js
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Jest fails all the time due to "Failed to cache transform results ...
Most of my calls to jest.runCLI (I run jest from a gulpfile ) end up with the following error: jest: failed to cache...
Read more >How can I clear the Jest cache? - Stack Overflow
As of Jest 22.0.0+, you can use the --clearCache option: Deletes the Jest cache directory and then exits without running tests.
Read more >Fix Jest's "failed to cache transform results in..EPERM
Fix Jest's "failed to cache transform results in..EPERM: operation not permitted" on Windows. jest, node, windows.
Read more >Configuring Vitest
At the moment Vitest stores cache for test results to run the longer and failed tests first. cache.dir #. Type: string; Default: node_modules/....
Read more >Hey guys has anyone seen this before when running builds on
Test suite failed to run jest: failed to cache transform results in: ... Just started today I'm wondering if I'm doing something wrong...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Let’s go with
patch-1
if you think it will fix the problem. This just involves adding:to
package.json
, correct?I think this fix will benefit other developers here (including reducing the flakiness on the CI, although I think I’ve seen this error exactly once, so I wouldn’t say it’s a very prevalent problem), so I’m in favor of getting it in.
Perhaps it is indeed time to evaluate if this can be removed. Thanks for looking into this @ksjogo!