Skip to content
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

thrown errors on hidden files e.g. .DS_Store #10

Closed
mikolayek opened this issue Aug 12, 2020 · 4 comments
Closed

thrown errors on hidden files e.g. .DS_Store #10

mikolayek opened this issue Aug 12, 2020 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@mikolayek
Copy link

Currently script scans directory and treats all files in selected directory as spec files.
I got error on .DS_Store, so it might occur with other files e.g. .gitignore.

It would be nice to have one of the options available:

  • hardcoded filtering files and include *.js only
  • possibility to define filter in -d option, or additional option, which will do filtering out for user

e.g.

# --include option
cypress-parallel -s cy:run -t 3 -d ./cypress/integration/examples --include *.js
# -- exclude option
cypress-parallel -s cy:run -t 3 -d ./cypress/integration/examples --exclude *.docx

Thrown error you can find below.

 npm
  ERR! code ELIFECYCLE
npm ERR! errno 1

 npm
 ERR! lenta-testing@1.0.0 cy:run: `cypress run "--reporter" "cypress-parallel/json-stream.reporter.js" "--spec" "'cypress/integration/examples/.DS_Store'"`
npm ERR! Exit status 1

 npm ERR!

npm ERR! Failed at the lenta-testing@1.0.0 cy:run script.

 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
@saki2rules
Copy link

I'm also facing the exact same issue.
Also version - 0.1.8 is not available on the npm. Can you please look into it.

@catchwhale
Copy link

catchwhale commented Jan 22, 2021

Seems to be an issue also from my side and its interesting concerned, hope we have any update on it

@mikolayek
Copy link
Author

Repository have bunch pull requests waiting for merge since July. I think it would be better to fork project and fix that issue by ourselves :(

@tnicola tnicola added the bug Something isn't working label Mar 16, 2021
@tnicola tnicola self-assigned this Mar 16, 2021
@sbagade-chwy
Copy link

I am facing the same problem. Any resolution to the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants