From ebf33c6e3b3ec94965c07defe2e79f7edec7f64d Mon Sep 17 00:00:00 2001
From: Trustin Lee <trustin@gmail.com>
Date: Sun, 19 Aug 2012 15:18:51 +0900
Subject: [PATCH] No need to make the timeout of thread model test too long

Using m1.large instance fixed the unstable build problem with CloudBees
---
 .../io/netty/channel/local/LocalTransportThreadModelTest.java   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/transport/src/test/java/io/netty/channel/local/LocalTransportThreadModelTest.java b/transport/src/test/java/io/netty/channel/local/LocalTransportThreadModelTest.java
index 2dfa9e005b..6e5c339ccc 100644
--- a/transport/src/test/java/io/netty/channel/local/LocalTransportThreadModelTest.java
+++ b/transport/src/test/java/io/netty/channel/local/LocalTransportThreadModelTest.java
@@ -204,7 +204,7 @@ public class LocalTransportThreadModelTest {
         }
     }
 
-    @Test(timeout = 120000)
+    @Test(timeout = 30000)
     public void testConcurrentMessageBufferAccess() throws Throwable {
         EventLoopGroup l = new LocalEventLoopGroup(4, new PrefixThreadFactory("l"));
         EventExecutorGroup e1 = new DefaultEventExecutorGroup(4, new PrefixThreadFactory("e1"));