-
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
ERR_CONNECTION_CLOSED (-100) loading 'https://app/__/#/tests/integration/home.test.js' #5482
Comments
Bafflingly, when Dependabot rebased the PR and the tests re-ran (https://circleci.com/gh/textbook/starter-kit/528), they worked, and when I re-run the example repo it works too. Don't know what changed over the weekend, but I'll close this out for now. |
This has come up again - a bunch more PRs from Dependabot (from textbook/starter-kit#87) have failed for the same reason as above. I've updated the example and it's failing locally again: https://github.com/textbook/cypress-test-tiny/tree/recreate-base-url-issue Cypress and |
This still happens if I build my own E2E container, based on https://docs.cypress.io/guides/guides/continuous-integration.html#Dependencies, so it's not a problem with FROM node:12.13.0-buster-slim
RUN apt-get update && apt-get install -y xvfb libgtk-3-dev libnotify-dev libgconf-2-4 libnss3 libxss1 libasound2
... |
The docker-compose Cypress tests were very unhappy on Circle, see cypress-io/cypress#5482.
I'm also seeing this after moving our CI Cypress runs from using |
Looks like this is related to #2996 and HSTS. I was using the service name |
@jakewisse you're right, nice catch; if I change the app name in
|
after some testing i found out that it had been broken here |
Wow, I had the exact same problem. |
Duplicate of cypress-io/cypress-docker-images#262 |
Current behavior:
Cypress seems to be trying to read the test files from entirely the wrong place (the HTTPS version of the
CYPRESS_BASE_URL
environment variable and thetests/
directory), when I run it in adocker-compose
network. As the app I'm testing doesn't serve those files, this fails.When I run the E2E tests normally, they pass: https://circleci.com/gh/textbook/starter-kit/443
However, when I run them in a network using
docker-compose
, they crash https://circleci.com/gh/textbook/starter-kit/437The error message is:
which suggests that Cypress is looking for the test files at the
CYPRESS_BASE_URL
and in the wrong directory; in that project (https://github.com/textbook/starter-kit) myintegrationFolder
is/e2e/integration
.It also mentions
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
as Cypress starts - I don't know if this is related, but it doesn't happen in the success case.Desired behavior:
I would like the Docker version to behave normally; I use this setup to regression test my code against multiple versions of Node.
Steps to reproduce: (app code and test code)
Test example repo: https://github.com/textbook/cypress-test-tiny/tree/recreate-base-url-issue
If you run Cypress in the container network (
npm run cypress:docker
), it fails with an error similar to the above complaint (and again looks in/tests
, not/cypress
):If you start the app (
npm start
) and then run Cypress with a base URL (CYPRESS_BASE_URL=http://localhost:3000 npm run cypress:run
), it seems fine, suggesting that it's not just the setting of the URL that's the problem.Versions
Cypress: 3.5.0 (I noticed this because it started failing when Dependabot PRd the upgrade: textbook/starter-kit#24)
OS: macOS 10.14.6 locally, also fails on CircleCI remotely
This happens with both
cypress/included:3.5.0
andcypress/included:3.3.1
; my first assumption was the problem was in trying to run Cypress 3.5 in the older image, but upgrading didn't help.The text was updated successfully, but these errors were encountered: