Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

https://github.com/karma-runner/karma fails on browserstack #159

Open
johnjbarton opened this issue Aug 27, 2019 · 4 comments
Open

https://github.com/karma-runner/karma fails on browserstack #159

johnjbarton opened this issue Aug 27, 2019 · 4 comments

Comments

@johnjbarton
Copy link
Contributor

The browserstack-based tests for karma project stopped working:
https://travis-ci.org/karma-runner/karma/jobs/577415432

Basically none of the browsers can be reached, eg:

27 08 2019 20:23:04.986:WARN [launcher.browserstack]: ie 11.0 (Windows 10) has not captured in 50000 ms, killing.
27 08 2019 20:23:06.223:WARN [launcher.browserstack]: chrome (Windows 10) has not captured in 50000 ms, killing.
27 08 2019 20:23:08.611:WARN [launcher.browserstack]: safari 9.0 (OS X El Capitan) has not captured in 50000 ms, killing.

Any suggestions?

@brandonocasey
Copy link

Probably this issue #152

@dweedon-stripe
Copy link

Also seeing this with ^1.4.0 so I'm not sure it is #152

@johnjbarton
Copy link
Contributor Author

22 10 2019 23:23:01.662:WARN [launcher.browserstack]: chrome (Windows 10) has not captured in 50000 ms, killing.

Basically browserstack does not work for us. Should we look for an alternative?

@samirans89
Copy link

samirans89 commented Feb 6, 2020

hi @johnjbarton,

Setting karma config timeout values in their Karma project for browser disconnects / timeouts have helped other users and recommended by BrowserStack support here: #61

As mentioned in the link, please check if the below values help in your Karma testing.
captureTimeout: 3e5, browserDisconnectTolerance: 3, browserDisconnectTimeout: 3e5, browserSocketTimeout: 1.2e5, browserNoActivityTimeout: 3e5,

Thanks,
Samiran

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants