-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Using --spec
option results in "no specs found" when project is located at Docker root directory
#23380
Comments
@BenDaSpur this issue was previously reported and fixed in 10.6.0, which was just released. Can you try 10.6.0 and report back? |
@tbiethman I am not having that issue anymore but on 10.6 I am getting this issue saying no spec files were found and in my config I have: |
@BenDaSpur hmm, are you running your command with a particular |
@tbiethman yes, this is what it looks like |
@BenDaSpur gotcha, that looks right. Can you share how you're using the container in a little more depth? It looks like you have your project files in the root directory, and are running cypress from the root directory? |
My entrypoint script is where that cypress run is happening. @tbiethman Let me know if you need more info |
@BenDaSpur thank you very much. I can reproduce this with a similar Dockerfile within our reproduction template repo:
The issue is that we're not properly handing projects at root with 10.5.0/10.6.0, specifically when the |
--spec
option results in "no specs found" when project is located at Docker root directory
The code for this is done in cypress-io/cypress#23535, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
All that changed is the version number in my dockerfile
If I downgrade from there to 10.4.0 I have no issues.
Desired behavior
Tests should run with no errors
Test code to reproduce
Build cypress/included:10.5.0
Try doing a
cypress run
Cypress Version
10.5.0
Node version
16.16.0
Operating System
Linux
Debug Logs
Other
No response
The text was updated successfully, but these errors were encountered: