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

Cypress could not connect to Firefox. Error: cannot open socket displayed at beginning of running spec #9621

Closed
snikaein opened this issue Dec 10, 2020 · 6 comments
Labels
browser: firefox stage: needs information Not enough info to reproduce the issue stale no activity on this issue for a long period

Comments

@snikaein
Copy link

snikaein commented Dec 10, 2020

When running cypress with options '--headless --browser firefox', cypress halts at the start of the second spec with message:

Cypress could not connect to Firefox.

An unexpected error was received from Marionette connection:

Error: cannot open socket

To avoid this error, ensure sure that there are no other instances of Firefox launched by Cypress running.

This blocks running all specs in 'run' mode

it seems this problem resolved just for windows platform at #6392 but we experience same via docker and Linux.

@Narretz
Copy link
Contributor

Narretz commented Dec 10, 2020

You probably should provide the versions of Cypress and Firefox (try latest if possible).

@jennifer-shehane
Copy link
Member

Yes, please provide Cypress version, Firefox version and the environment details of your run including OS.

@jennifer-shehane jennifer-shehane added the stage: needs information Not enough info to reproduce the issue label Dec 11, 2020
@snikaein
Copy link
Author

@jennifer-shehane @Narretz

cypress version: 5.5.0
FIREFOX_VERSION=82.0.3
Docker base image: node:14.15.1-buster which is Debian 10.6

We ran our test in parallel via 20 containers and we have around 150 specs via 700 tests.
we understand during each test Firefox close and open before each spec which is 150 times across the 20 containers and only one time this issue happened in some test runs which means very rare issue but still makes 25% of our total runs failed because of this issue.

@snikaein
Copy link
Author

snikaein commented Dec 11, 2020

for sure this issue not catch able via your test which in run very few tests and specs and way different than scale we use.
I have to mention we had socket error issue even before via CentOS docker base image and chrome multiple versions which makes me believe should be some problem in cypress side.
issues like #8986 , #8674, # #8986 and lot more if needs to be addressed.

@snikaein
Copy link
Author

snikaein commented Dec 11, 2020

Another suggestion for case like this, as we use cypress in parallel mode in CI, cypress could have some recovery method(like flaky test) since we have available machine to handle the tests and not return error(which make any CI failed) if could not connect to Firefox in single machine.

@cypress-app-bot
Copy link
Collaborator

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

@cypress-app-bot cypress-app-bot added the stale no activity on this issue for a long period label May 17, 2023
@cypress-app-bot cypress-app-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser: firefox stage: needs information Not enough info to reproduce the issue stale no activity on this issue for a long period
Projects
None yet
Development

No branches or pull requests

4 participants