Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Testing process on SauceLabs doesn't complete properly
See original GitHub issueWhen tests are running on SauceLabs, the process fails. Here’s the last relevant message:
09 05 2020 16:58:47.168:WARN [launcher]: Chrome on SauceLabs have not captured in 60000 ms, killing.
See an example failed build here: https://travis-ci.org/github/Aaronius/penpal/builds/685098099
I’ve tried several configuration changes but haven’t had success fixing the problem. Alternatively, explore different testing solutions entirely.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Common Error Messages | Sauce Labs Documentation
Below are some Sauce Labs automated testing common error messages and how to fix them.
Read more >Troubleshooting Selenium Test Scripts
Troubleshooting Selenium Test Scripts · Open Commands time out, even though I see the app loaded in the video. · My test that...
Read more >Test Configuration Options | Sauce Labs Documentation
An index of automation test configuration settings compatible with Sauce Labs test protocols.
Read more >Best Practices for Running Tests - The Sauce Labs Cookbook
From runnings tests in parallel to how to use small, atomic, autonomous tests check out this comprehensive guide on best practices for running ......
Read more >Error Messages on Sauce and What They Mean
1. You're running too many tests at a time: Check the left sidebar on your Account page. It shows a "Parallel tests" number,...
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 Free
Top 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
One option would be to ditch TravisCI and use the Sauce Labs CLI in conjunction with GitHub actions.
I’m happy to submit a PR with the workflow, then you can add your Sauce Labs credentials to a GitHub secret.
Okay, the secrets are set!