-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script failed when 'runner-results' folder not exist or if not empty #56
Comments
Hey @PBIIBP . I'm having the same problem and actually even if I create the empty Did you managed to overcome this issue somehow? |
changing the cleanResultsPath method in node_modules/cypress-parallel/cli.js to the following did the trick for me:
|
@PBIIBP May be issue is with your cypress-report-config.json file. Can you share the json file ? |
I encountered the same issue with version cypress-parallel 0.9.0 and cypress 9.4.1 Would be great if you can have a look @ISanjeevKumar node:fs:1390 Error: ENOENT: no such file or directory, scandir 'C:\Users\user\dev\project\runner-results' |
I understood the problem now. it is getting failed because : When none of the test case has got executed then report folder will not get created by 'json-stream.reporter', Hence you are getting this error. Command which you are using looks not correct to me. Please use something like this '"node_modules/.bin/cypress-parallel -s dev -t 2-d '**/user.spec.ts'. Note: json-stream.reporter will create report folder 'runner-result' only when a test case gets executed. |
HI @ISanjeevKumar, sorry for the late response to your suggestion.
I can confirm if none test cases are found this error will occour. In our case tests where executed but still the error will occour.
This is exactly what npx does from my understanding. https://www.npmjs.com/package/npx |
I did some investigation today and can give the following result in return which lead to the error in our case.
My question here is if it is intended that cypress-multi-reporters config from cypress.json will be ignored by default? Its at least not documented. |
@nils-hoyer nils-hoyer |
yes, I addressed the reporter-config.json from the cypress-parallel cli. two suggestions: make sure, you are not using cypress-extends plugin and not refer to report-config file from cypress config. |
Sorry, doesn't seems to work for me. Even if I remove the reporter config complete. |
if you upload an example repo reproducing the error I can have a quick look on it. |
I have this somewhat similar issue. Unfortunately i cannot share the repo is a customer project, but i run the build without parallel it works all fine on jenkins but everytime i try it out with parallel i get this error.
this started to happen after cypress 10 upgrade, but works well with cypress 9 |
I am facing the same problem |
Same problem. Will check up on the PR linked above. |
Hi,
in the start script, there is a line code that remove the 'runner-results' folder but the script throw an exception in 2 cases:
-> when this folder not exist
-> when this folder exist and it contains files
So before run the cmd, i must clean the folder or create a empty 'runner-results' folder. Could you handle this exception?
(node:30920) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, rmdir 'C:\Personal_Unsaved\Projet\front-end\runner-results'
at Object.rmdirSync (fs.js:684:3)
at cleanResultsPath (C:\Personal_Unsaved\Projet\front-end\node_modules\cypress-parallel\cli.js:19:6)
at start (C:\Personal_Unsaved\Projet\front-end\node_modules\cypress-parallel\cli.js:23:3)
at Object. (C:\Personal_Unsaved\Projet\front-end\node_modules\cypress-parallel\cli.js:124:1)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
(node:30920) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:30920) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered: