After upgrading to 6.3.0 getting "Error: EPERM: operation not permitted, unlink"
See original GitHub issueCurrent behavior
After upgrading to 6.3.0 getting flaky errors on different tests, all the same:
11:50:05 EPERM: operation not permitted, unlink 'C:\Users\Administrator\AppData\Roaming\Cypress\cy\production\browsers\chrome-stable\run-2668\CypressCache\data_0'
11:50:05 Error: EPERM: operation not permitted, unlink 'C:\Users\Administrator\AppData\Roaming\Cypress\cy\production\browsers\chrome-stable\run-2668\CypressCache\data_0'
Desired behavior
no errors
Test code to reproduce
random
Versions
last known working: 6.2.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Error: EPERM: operation not permitted, unlink 'D:\Sources ...
I was able to fix this by running the command prompt/bash as admin and closing VSCode! Seems like VSCode was locking some files....
Read more >Npm failed with return code: 4294963248, Error: EPERM
We have the `npm install` task that suddenly fails with Error: EPERM: operation not permitted, unlink 'C:\....\tsserver.js'. This was not happening before ...
Read more >sfdx update fails, Error: EPERM: operation not permitted
I was facing the same error right now. I added the location to environment variables and its working fine now.
Read more >error[EPERM]Operation not permitted - Kibana - Elastic Discuss
I installed Elasticsearch with msi file and did Kibana with zip file and unzip. I got Auto password for all applications previously and...
Read more >"Error: EPERM: operation not permitted, rename" on npm install
Occasionally, my build will fail. Re-running it will cause it to be fixed. Here is a failed build example.
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
Can everyone try to update to 6.4.0? We did revert a change from 6.3.0 in that release - although I’m not sure how it is related exactly.
Also getting this error on Azure Pipeline with v6.3.0. Didn’t faced this before. Also didn’t enable the experimental studio option.