Cypress always times out on Github Actions [Help Request]
See original GitHub issueMy flow was working fine and I have not changed any settings, but now it times out on every PR. I look through the commits and it sure seems like nothing has changed, anyway.
Outside of opening a PR without my cypress.yml, and then putting it back in, is there anything else I can check to see why it wouldn’t run? I have tried the various flavors of cypress 9.x.x and that has no impact.
Thanks for any insight.
Here is my YML
on: [pull_request]
env:
CYPRESS_REACT_APP_API_URL: https:/xxxxx
REACT_APP_API_URL: xxxxxxxx
jobs:
cypress-run:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Setup kernel and increase watchers
run: echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
# Install NPM dependencies, cache them correctly
# and run all Cypress tests
- name: Cypress run
uses: cypress-io/github-action@v2
with:
quiet: false
browser: chrome
headless: true
record: false
start: npm start
wait-on: http://localhost:3000
wait-on-timeout: 180
env: true
env:
REACT_APP_RECAPTCHA_SITE_KEY: xxxxxx
CYPRESS_REACT_APP_API_URL:xxxxx
REACT_APP_API_URL: xxxxx
CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Issue Analytics
- State:
- Created a year ago
- Reactions:8
- Comments:6
Top Results From Across the Web
GitHub Actions - Cypress Documentation
The Cypress team maintains the official Cypress GitHub Action for running Cypress tests. This action provides npm installation, custom caching, additional ...
Read more >Complete Guide To Cypress Testing With GitHub Actions
Read on this blog to learn how to set up CI/CD pipeline for test cases using Cypress with GitHub Actions.
Read more >Recording with GitHub Actions - Docs
Using Replay's action-cypress in your GitHub Actions workflow is the easiest way to get started recording your Cypress tests in CI.
Read more >cypress-io/cypress - Gitter
Should this custom command work to send a default timeout of 6s to the get command ... I was able to test locally...
Read more >Cypress and Flaky Tests: How to Handle Timeout Errors
In the context of testing a web application, a timeout error may occur when the app runs an asynchronous operation that must complete...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same for me. Solved it by replacing
localhost
with127.0.0.1
.From the Cypress changelog:
Unfortunately I am also experiencing this issue. I wanted to run Cypress on Node v18. This also caused a timeout. LTS version 16.15.0 is working.
One of the differences I see in logs (Before there was also a network address.):
Full error log:
Setup package.json: scripts:
devDependencies:
If you want to know more scripts and package versions, let me know.