From 6f776102b23f413f7f2443efe62beaac2be91add Mon Sep 17 00:00:00 2001
From: Vojta Jina <vojta.jina@gmail.com>
Date: Mon, 14 Jul 2014 17:34:53 -0700
Subject: [PATCH] chore(travis): increase browserNoActivityTimeout
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

We’ve seen many failures recently because of Karma killing a browser
after browserNoActivityTimeout. It’s possible that this is not any issue
other than super slow network / proxy.

Will try higher timeout and observe for a while.
---
 karma-shared.conf.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/karma-shared.conf.js b/karma-shared.conf.js
index 6d4f2d13..cd80f1a6 100644
--- a/karma-shared.conf.js
+++ b/karma-shared.conf.js
@@ -9,7 +9,7 @@ module.exports = function(config, specificOptions) {
     browsers: ['Chrome'],
     browserDisconnectTimeout: 10000,
     browserDisconnectTolerance: 2,
-    browserNoActivityTimeout: 20000,
+    browserNoActivityTimeout: 30000,
 
 
     // SauceLabs config for local development.