From 11be8c3733a2192fc074a557c9430709f339ee25 Mon Sep 17 00:00:00 2001
From: Brian Gough <bjg@network-theory.co.uk>
Date: Fri, 27 Nov 2015 14:13:46 +0000
Subject: [PATCH] increase timeout in lock manager test

on heavily loaded machines 20ms isn't long enough to consistently get
multiple calls to the lock manager
---
 .../test/unit/coffee/LockManager/LockManagerTests.coffee        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/services/track-changes/test/unit/coffee/LockManager/LockManagerTests.coffee b/services/track-changes/test/unit/coffee/LockManager/LockManagerTests.coffee
index 298665a00b..266b12b120 100644
--- a/services/track-changes/test/unit/coffee/LockManager/LockManagerTests.coffee
+++ b/services/track-changes/test/unit/coffee/LockManager/LockManagerTests.coffee
@@ -103,7 +103,7 @@ describe "LockManager", ->
 				startTime = Date.now()
 				@LockManager.LOCK_TEST_INTERVAL = 5
 				@LockManager.tryLock = (doc_id, callback = (error, isFree) ->) ->
-					if Date.now() - startTime < 20
+					if Date.now() - startTime < 100
 						callback null, false
 					else
 						callback null, true