-
Notifications
You must be signed in to change notification settings - Fork 354
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
Impossible to activate headed mode #403
Comments
Seeing the same issue. It's especially annoying when running visual regression tests, because From what I see in the code it doesn't even look for the |
+1 |
realized this today after trying headless: false and seeing it still run in headless mode. seems misleading to me if the headless option is always the default anyway, would really appreciate a headed option update: as a workaround i was able to get headed mode working by using the
|
Thank you, @andrewalc!
|
I noticed the same. - name: 'Run end-to-end tests'
id: cypress
timeout-minutes: 15
uses: cypress-io/github-action@v5 # see https://github.com/cypress-io/github-action/issues/620
env:
ELECTRON_EXTRA_LAUNCH_ARGS: '--disable-gpu' # see https://github.com/cypress-io/cypress/issues/25357
with:
working-directory: 'e2e-tests'
config: 'specPattern="**/*.cy.ts"'
env: 'host="${{ steps.setup.outputs.deployment_url }}",username="${{ steps.setup.outputs.deployment_username }}",password="${{ steps.setup.outputs.deployment_password }}"'
browser: '${{ steps.setup.outputs.browser }}'
headed: false
|
I don't see any remaining problem with Could you please explain what you think should be different? In your example you specified |
You are absolutely correct! I misinterpreted the action option. :shame: Should I delete these messages, to avoid confusing other users? |
Since you have commented on this stale issue it has become reactivated in the triage process. I did check that So I suggest to leave your comments and wait for a member of the Cypress team to pick up this issue. My recommendation would be to close this issue as it is resolved and no longer reproducible. |
Closing as resolved |
when running specs locally with "cypress open" (headed), they pass. they fail locally when running "cypress run"(headless) for timeout issues. ci also runs headless, and gets timeout issues. I'm updating the config to run headed in ci in an attempt to get them to pass. ref: cypress-io/github-action#403 (comment)
the change in 3479ce0 still erred. I created a new script for the cypress workflow to call specifically. ref: cypress-io/github-action#403 (comment)
Hi,
It seems impossible to activate headed mode with Cypress (8.0) and its Github action.
Look at https://github.com/nboisteault/lizmap-web-client/runs/3134874027?check_suite_focus=true#step:9:5 , I did put :
But action is ran headless : https://github.com/nboisteault/lizmap-web-client/runs/3134874027?check_suite_focus=true#step:9:51
Thanks for you help.
The text was updated successfully, but these errors were encountered: