cypress: Firefox hangs sometimes when running in cypress/included:4.0.1
Cypress v4.0.1 installed in cypress/included:4.0.1 with Firefox 72
Running via docker-compose in repo https://github.com/cypress-io/cypress-example-docker-compose-included on CircleCI
There are 3 jobs in the Circle workflow https://circleci.com/gh/cypress-io/workflows/cypress-example-docker-compose-included/tree/master test-electron and test-chrome usually pass without any problems (they are running our Kitchensink tests against example.cypress.io), while FF usually hangs during one the specs (different specs)
You can search test-firefox among jobs here https://circleci.com/gh/cypress-io/cypress-example-docker-compose-included/tree/master
so it could be a crash inside the container, but we don’t know
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 5
- Comments: 28 (5 by maintainers)
Commits related to this issue
- CI: add timeout to e2e step. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issues/6449 — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
- CI: disable multiprocess mode in Firefox when running e2e. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issu... — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
- CI: add timeout to e2e step. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issues/6449 — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
- CI: disable multiprocess mode in Firefox when running e2e. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issu... — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
- CI: add timeout to e2e step. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issues/6449 — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
- CI: disable multiprocess mode in Firefox when running e2e. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issu... — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
- CI: add timeout to e2e step. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issues/6449 — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
- CI: disable multiprocess mode in Firefox when running e2e. - Sometimes cypress hang indefinitely in the CI which makes this step run for almost an hour. See https://github.com/cypress-io/cypress/issu... — committed to kitspace/kitspace-v2 by AbdulrhmnGhanem 3 years ago
I also faced similar issue. Setting MOZ_FORCE_DISABLE_E10S=1 env variable solved the issue for me. This disables the multiprocess mode in Firefox
Can someone please look into this issue?
I would like to confirm that setting
MOZ_FORCE_DISABLE_E10S=1, according to @michalziolek’s comment, also worked for me.I am running both Chrome and Firefox browsers with the
--headlessoption in a GitLab CI Docker. Firefox would hang until the CI job timed-out.@lipowiczNeurosys increasing
--shm-size=2gwas the ticket for me in GitHub actions, see my research into this here: https://github.com/cypress-io/github-action/issues/104Using
MOZ_FORCE_DISABLE_E10Sdidn’t seem to work in headed/headless mode, though I may not have put it at the right level (I tried on theuses: cypress-io/github-action@v2step, not the job or container).Any updates on this? @Bkucera We have to unfortunately disable e2e because no solution or fix is being provided for this. A lot of us are facing this problem. Can anyone atleast start looking into this?
@jennifer-shehane @Bkucera Outside of a reproduction what is useful to help diagnose what is going on here? In our case, we have had to disable CI tests, which I am not okay with, so would love to see some movement on the tickets @vivek12345 pointed out all seem to be related.
@bahmutov have you try to assign more shared memory for a docker container? I mean to run docker image with the following parameter i.e.
docker run --shm-size=1g. I think that I have a similar issue, but I found kind of workaround (at least in my local docker run).I’m seeing similar behavior with our tests using Gitlab CI. Chrome runs fine, whereas Firefox will hang indefinitely for random specs.