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.
Travis CI fails on browser-stack tests:client
See original GitHub issueSo the post-commit tests (running off the master fork) fail on Travis.
The browser-stack tests:client only run on the master fork. That is a combination of the line
const TRAVIS_WITH_BS = !!process.env.BROWSER_STACK_ACCESS_KEY
https://github.com/karma-runner/karma/blob/master/test/client/karma.conf.js#L3 and the setting in the Travis config that marks the key as master-branch only.
But there is a copy that is marked for travis branch only, so pushing to that branch should trigger browserstack without walking on master.
The failures on Travis are timeouts; the browserstack viewer shows karma in the browser with just “Karma-Starting” on the page.
I will try to run with DEBUG logging and concurrency 1. Could this be a socket.io issue?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
🎉 This issue has been resolved in version 6.0.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
After updating to v6.0.0 we are getting Safari failures ourselves https://github.com/twbs/bootstrap/runs/1707340240. Going back to v5.x works again.
Sounds like it’s the same issue? Although, we are still using karma-browserstack-launcher 1.4.0 because the newer ones has other issues I couldn’t solve.