Increase test runner speed.

test/cctest/cctest.status

Index: test/cctest/cctest.status
diff --git a/test/cctest/cctest.status b/test/cctest/cctest.status
index a596add43abf8bd5202d3f3abea575a04fbf40ad..267e392872a4cb15e99ab68e137eba1c61a0a6a3 100644
--- a/test/cctest/cctest.status
+++ b/test/cctest/cctest.status
@@ -60,6 +60,11 @@
   # running several variants. Note that this still takes ages, because there
   # are actually 13 * 38 * 5 * 128 = 316160 individual tests hidden here.
   'test-parsing/ParserSync': [PASS, NO_VARIANTS],
+
+  ############################################################################
+  # Slow tests.
+  'test-api/Threading1': [PASS, ['mode == debug', SLOW]],
+  'test-api/Threading4': [PASS, ['mode == debug', SLOW]],

[Yang, 2013/11/26 15:52:30]

Threading* tests are a summary of essentially normal tests that are defined
using the THREADED_TEST macro instead of TEST. So we already have
single-threaded coverage on those tests, but run them multi-threaded again. In
order to reduce runtime, Threading tests are divided into four parts. It just
happens that parts 2 and 3 are somewhat faster, but it seems arbitrary to me to
mark only 1 and 4 as slow.

Imo we can remove all 4 parts.

Or divide them into more parts, but that probably wouldn't make the total run
time any faster.

 }],  # ALWAYS
 
 ##############################################################################
@@ -89,6 +94,10 @@
   'test-serialize/DeserializeFromSecondSerializationAndRunScript2': [SKIP],
   'test-serialize/DeserializeAndRunScript2': [SKIP],
   'test-serialize/DeserializeFromSecondSerialization': [SKIP],
+
+  ############################################################################
+  # Slow tests.
+  'test-api/Threading1': [PASS, SLOW],
 }],  # 'arch == arm'
 
 ##############################################################################