[CI] Verify why BrowserStack times out all the time #1778
Labels
resolution:duplicate
This issue is a duplicate of another issue and was merged into it.
type:task
This issue reports a chore (non-production change) and other types of "todos".
About 50% of jobs end with BrowserStack time outing. Not sure if the problem is on BS's or Travis's side or an integration between Karma and BS. We need to figure this out because it makes our CI useless.
The text was updated successfully, but these errors were encountered: