search

karma-runner / karma-browserstack-launcher

A Karma plugin. Launch any browser on BrowserStack!
MIT License
150 stars 82 forks source link

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

Open johnjbarton opened 5 years ago

johnjbarton commented 5 years ago

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 commented 5 years ago

Probably this issue https://github.com/karma-runner/karma-browserstack-launcher/issues/152

dweedon-stripe commented 5 years ago

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

johnjbarton commented 5 years ago

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 commented 4 years ago

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: https://github.com/karma-runner/karma-browserstack-launcher/issues/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