upping timeout value to help tests finish, so the long ones can be measured.

releng.wtpbuilder/distribution/wtp.tests/build.xml

@@ -149,9 +149,12 @@
         time out may need to be set/adjust for api or performance tests?
         This testTimeLimit is the whole, overall limit on tests. There's
         a shorter one for individual suites. some common values, of
-        milliseconds to more recognizable units: 14400000: 4 hours ...
-        up'd to 4 hours after P2 7200000: 2 hours 3600000: 1 hour
-        1800000: 30 minutes 600000: 10 minutes
+        milliseconds to more recognizable units: 
+        14400000: 4 hours
+        7200000: 2 hours 
+        3600000: 1 hour  
+        1800000: 30 minutes 
+        600000: 10 minutes
     -->
     <property
         name="testTimeLimit"

releng.wtpbuilder/distribution/wtp.tests/testScripts/wtp-junit-tests.xml

@@ -46,9 +46,11 @@
         <property
             name="testRoot"
             value="${testRoot}"/>
+    	  <!-- temporarily changed from 30 minutes (1800000) to 2 hrs (7200000) 
+    	  to help spot problematic tests -->
         <property
             name="timeout"
-            value="1800000"/>
+            value="7200000"/>
         <property
             name="junit-report-output"
             value="${junit-report-output}"/>