From 6c86ba45ef1e9b03dfdc1fa1ae9b1692e29b6f92 Mon Sep 17 00:00:00 2001
From: Paul Phillips <paulp@improving.org>
Date: Sat, 1 May 2010 17:17:56 +0000
Subject: Kicked the partest timeouts way up since appare...

Kicked the partest timeouts way up since apparently even 6 hours isn't
enough for windows to complete. Don't know what the deal is there, let's
see if 10 hours is enough. No review.
---
 build.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/build.xml b/build.xml
index 31acda4280..58373ea69b 100644
--- a/build.xml
+++ b/build.xml
@@ -1502,9 +1502,9 @@ BOOTRAPING TEST AND TEST SUITE
   <target name="test.suite" depends="pack.done">
     <partest classpathref="pack.classpath">
       <env key="PATH" path="${build-pack.dir}/bin:${env.PATH}" />
-      <sysproperty key="partest.timeout" value="21600" />
-      <sysproperty key="partest.test-warning" value="150" />
-      <sysproperty key="partest.test-timeout" value="1200" />
+      <sysproperty key="partest.timeout" value="36000" />
+      <sysproperty key="partest.test-warning" value="300" />
+      <sysproperty key="partest.test-timeout" value="1800" />
       <sysproperty key="partest.srcdir" value="files" />
       <sysproperty key="partest.scalacopts" value="${scalac.args.all}" />
       <sysproperty key="partest.javacopts" value="${javac.args}" />
-- 
cgit v1.2.3