Error spawn UNKNOWN during `cypress run`
See original GitHub issueNot able to run my spec files using the below mentioned command
npx cypress run --spec <spec path>
Getting Error:
Warning: We failed to trash the existing run results.
This error will not alter the exit code.
spawn UNKNOWN
Error: spawn UNKNOWN
at ChildProcess.spawn (internal/child_process.js:394:11)
at spawn (child_process.js:553:9)
at C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\processor.js:152:24
at FfmpegCommand.proto._getFfmpegPath (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\capabilities.js:90:14)
at FfmpegCommand.proto._spawnFfmpeg (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\processor.js:132:10)
at FfmpegCommand.proto.availableFormats.proto.getAvailableFormats (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\capabilities.js:517:10)
at C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\capabilities.js:568:14
at nextTask (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\node_modules\async\dist\async.js:4576:27)
at Object.waterfall (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\node_modules\async\dist\async.js:4587:9)
at Object.awaitable (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\node_modules\async\dist\async.js:208:32)
at FfmpegCommand.proto._checkCapabilities (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\capabilities.js:565:11)
at C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\processor.js:298:14
at nextTask (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\node_modules\async\dist\async.js:4576:27)
at Object.waterfall (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\node_modules\async\dist\async.js:4587:9)
at Object.awaitable (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\node_modules\async\dist\async.js:208:32)
at FfmpegCommand.proto._prepare (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\processor.js:295:11)
at FfmpegCommand.proto.exec.proto.execute.proto.run (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\processor.js:431:10)
at FfmpegCommand.proto.saveToFile.proto.save (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fluent-ffmpeg\lib\recipes.js:28:25)
at C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\lib\video_capture.js:191:20
at Promise.cancellationExecute [as _execute] (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\debuggability.js:449:9)
at Promise._resolveFromExecutor (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:518:18)
at new Promise (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:103:10)
at startCapturing (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\lib\video_capture.js:132:14)
at Object.start (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\lib\video_capture.js:195:12)
at C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\lib\modes\run.js:669:6
at tryCatcher (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:547:31)
at Promise._settlePromise (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:604:18)
at Promise._settlePromise0 (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:649:10)
at Promise._settlePromises (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:729:18)
at Promise._fulfill (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:673:18)
at C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\nodeback.js:42:21
at C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fs-extra\lib\mkdirs\mkdirs.js:56:16
at callback (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\fs-extra\node_modules\graceful-fs\polyfills.js:295:20)
at callback (C:\Users\<username>\AppData\Local\Cypress\Cache\4.1.0\Cypress\resources\app\packages\server\node_modules\graceful-fs\polyfills.js:289:20)
at FSReqCallback.oncomplete (fs.js:166:5)
I would like to run all my spec files in integration folder
Versions 4.1.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Error spawn UNKNOWN during · Issue #20842 · cypress-io ...
Now, I'm able to perform both tasks. Launch cypress from command prompt and also from VS code terminal; Run cypress using cypress run...
Read more >during first cypress run getting error spawn EPERM on ...
This is usually caused by a missing library or dependency. The error below should indicate which dependency is missing. https://on.cypress.io/ ...
Read more >cypress-io/cypress - Gitter
I am trying to run cypress using command prompt-Headless - and i am getting an spawn UNKNOWN error .This is the command i...
Read more >Cypress not running after installing on windows 32bit
Bug : After the installation through npm I tried to open cypress. It fails with the following error message: ...
Read more >How to fix this Error: spawn EACCES
This error comes up when you don't have full permissions to the project folder. You want to run the chmod command in order...
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 FreeTop 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
Top GitHub Comments
Since this issue hasn’t had activity in a while, we’ll close the issue until we can confirm this is still happening. Please comment if there is new information to provide concerning the original issue and we’d be happy to reopen.
Additional Info: I have same configuration in my personal laptop over there when I try to execute all spec using command:
“test:all”:“cypress run --browser chrome --headed” --> from the package.json
npm run test:all
Appreciate a response and resolution as soon as possible.