Cypress dashboard runs duration not ending
See original GitHub issueBUG
Current behavior:
Desired behavior:
Runs to have some timeout
Steps to reproduce:
https://github.com/gpincheiraa/bln-frontend-project1/tree/cypress_dashboard https://travis-ci.org/gpincheiraa/bln-frontend-project1/builds/388817066
When I push to a branch, Travis CI comes to action, even tells the project and run
commands used were:
npm start & (wait-on http://localhost:3000 && cypress run --record --key 27df0bb4-b483-4074-9299-def2f76ff852)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Runs
Recorded runs capture the results from your test runs. If you haven't set up ... At the bottom of the run duration graph...
Read more >Troubleshooting
Open Cypress via cypress open · Go to Developer Tools -> View App Data · This will take you to the directory in...
Read more >Testing Your App
Once your server is running, it's time to visit it. Let's delete the sample.cy.js file created in the previous tutorial now that it's...
Read more >Test and debug faster with Cypress Cloud
Fast, easy and reliable testing for anything that runs in a browser. Install Cypress in seconds and take the pain out of front-end...
Read more >Changelog
Fixed an issue where the Cypress migration wizard would fail to run in global mode ... if a project is connected to the...
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
I am seeing this with Circle CI under the follow conditions:
Cypress Dashboard shows runs running forever (one for > 8 days).
This issue will be closed to further comment as the exact issue here was resolved and tested.
If you’re experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.