You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running the dev server and before the Cypress run I get thousands of logs about exceeding file watchers.
Curious if this is something that can be rectified via the plugin interface somehow or if it's an issue with Github Actions? The test eventually runs fine, but in order to see the results you have to scroll through thousands of logs to find them.
Workflow config
name: Cypress end-to-end tests
on: [push]
jobs:
cypress-run:
runs-on: ubuntu-16.04
steps:
- name: Checkout
uses: actions/checkout@v2
with:
persist-credentials: false
# Install NPM dependencies, cache them correctly
# and run all Cypress tests
- name: Cypress run
uses: cypress-io/github-action@v2
with:
start: npm start
wait-on: http://localhost:4000
wait-on-timeout: 6000
The text was updated successfully, but these errors were encountered:
I was able to fix this by including CHOKIDAR_USEPOLLING=1 in my start command.
Ultimately it looks like it's not an issue with this action but with Gatsby's dev server. Got the idea from this thread in Gatsby's repo: gatsbyjs/gatsby#15843
After running the dev server and before the Cypress run I get thousands of logs about exceeding file watchers.
Curious if this is something that can be rectified via the plugin interface somehow or if it's an issue with Github Actions? The test eventually runs fine, but in order to see the results you have to scroll through thousands of logs to find them.
Workflow config
The text was updated successfully, but these errors were encountered: