Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

karma conf: prevent timeouts on Travis CI #1153

Merged
merged 1 commit into from
Mar 3, 2015

Conversation

bajtos
Copy link
Member

@bajtos bajtos commented Mar 3, 2015

Increase the timeout values to prevent DISCONNECTED errors when
running the tests on slow machines (e.g. Travis CI).

Increase the timeout values to prevent DISCONNECTED errors when
running the tests on slow machines (e.g. Travis CI).
@bajtos bajtos added the #review label Mar 3, 2015
@bajtos
Copy link
Member Author

bajtos commented Mar 3, 2015

Here we go, Travis builds are green again 🎯

bajtos added a commit that referenced this pull request Mar 3, 2015
…avis

karma conf: prevent timeouts on Travis CI
@bajtos bajtos merged commit 03ad328 into master Mar 3, 2015
@bajtos bajtos deleted the fix/phantomjs-timeouts-on-travis branch March 3, 2015 09:07
@bajtos
Copy link
Member Author

bajtos commented Mar 3, 2015

For posterity, here is some info that helped me to solve this issue.

karma-runner/karma#598

I've noticed that using pre-processors can cause this to increase as well.
Since karma launches the browser then processes all the files. If your
preprocessors take a long time to run then I'll bet you see a direct
correlation.

codymikol/karma-webpack#8

I've solved the issue by increasing the browserNoActivityTimeout in karma
config. It seems it took too long to compile a bundle so the browser was
killed before the bundle was ready.

// Timeout for capturing a browser (in ms).
captureTimeout: 60 * 1e3,

// to avoid DISCONNECTED messages
browserDisconnectTimeout : 10000, // default 2000
browserDisconnectTolerance : 1, // default 0
browserNoActivityTimeout : 60 * 1e3, //default 10000

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

Successfully merging this pull request may close these issues.

None yet

1 participant