From a2b64798f7504025472123cf5c347746fb1acd0e Mon Sep 17 00:00:00 2001
From: David Baker <dave@matrix.org>
Date: Tue, 5 Jul 2016 14:34:33 +0100
Subject: [PATCH] Fix timelinepanel test timeout

The previous fix was adjusting the wrong timeout: it's hitting browserNoActivityTimeout, so revert previous fix & do this instead
---
 karma.conf.js                                    | 1 +
 test/components/structures/TimelinePanel-test.js | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/karma.conf.js b/karma.conf.js
index 1ae2494add..45f5dd9998 100644
--- a/karma.conf.js
+++ b/karma.conf.js
@@ -171,5 +171,6 @@ module.exports = function (config) {
             },
             devtool: 'inline-source-map',
         },
+        browserNoActivityTimeout: 15000,
     });
 };
diff --git a/test/components/structures/TimelinePanel-test.js b/test/components/structures/TimelinePanel-test.js
index de547b1779..045ccd70b7 100644
--- a/test/components/structures/TimelinePanel-test.js
+++ b/test/components/structures/TimelinePanel-test.js
@@ -210,7 +210,7 @@ describe('TimelinePanel', function() {
         var N_EVENTS = 600;
 
         // sadly, loading all those events takes a while
-        this.timeout(N_EVENTS * 40);
+        this.timeout(N_EVENTS * 20);
 
         // client.getRoom is called a /lot/ in this test, so replace
         // sinon's spy with a fast noop.