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
Circle-ci binary installation process fails #2344
Comments
I think #2340 is the same issue |
@paulfalgout just out of curiosity, do you also see installation issues whenever Cypress releases a new version? |
We'll I've only had this problem the once, but I've only updated from a v3.x to another v3.x once as well, which I think is part of the issue. Do you have cypress installed in multiple workspaces? I had attributed my issue to that. |
We actually only depend on cypress in one package, so that would at least mean that our issue is not attributable to multiple versions |
hi cypress team! would it be possible to get some updates here? have you guys experimented with installing cypres binaries from within yarn workspaces? |
It's likely this is a bug in the cli, I will look into this, thanks for all the detailed info |
Hey @bkucera @jennifer-shehane any luck w this issue? |
@mechanical-turk where do you see Cypress
Is it possible your |
Also, globally installing cypress isn't recommended, because it can cause errors like this with mismatched versions |
This also happens when having multiple cypress deps of the same version See #4595 @mechanical-turk Any update on your side? |
@jennifer-shehane we could not find a solution so we ended up temporarily disabling cypress on our CI layer. It's kinda funny but nowadays we run our tests locally and not on CI anymore. I'm sure that if you folks keep up your good work, it'll be resolved in no time! |
@paulfalgout can you please explain how did you solve that? I am switching from one version to another and getting the same issue. |
Closing as duplicate of #4595 as I don't see any evidence that this is happening outside of yarn workspaces. If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix. |
Our issue came from switching from npm to yarn in circleci. We got this error: The solution was to persist the cypress/* folder:
|
Current behavior:
The binaries fail to install the correct version on circle-ci as part of the post-install script.
Here's some background:
yarn install
just simply failed to install the binaries during post-install. For that reason, we opted in for a hacky solution where we rannpm install cypress 3.0.3
afteryarn install
was completed.3.0.3
is the cypress version in our package json.3.0.1
, even though both the package.json, and the npm install versions are3.0.3
.Not sure if this is helpful, but here's the error log from cypress:
There are 2 useful tips in here:
We currently have caching disabled, so I'm not sure how to proceed here.
Desired behavior:
The desired behavior is for cypress to understand that we want to use
v3.0.3
, and notv3.0.1
.Steps to reproduce:
Versions
The text was updated successfully, but these errors were encountered: