build: give windows builders extra time for tests

In the tests, the runtime test fails after 2 minutes.
On an unloaded VM it only takes 45 seconds.
I think the difference is all the other build work going on
simultaneously with the running of the runtime test.

Change-Id: I41e95d2e4daea44ceaa8505f81aa7b5bcfa9ec77
Reviewed-on: https://go-review.googlesource.com/6364
Reviewed-by: David Crawshaw <crawshaw@golang.org>
Reviewed-by: Minux Ma <minux@golang.org>
Reviewed-by: Alex Brainman <alex.brainman@gmail.com>

diff --git a/src/run.bat b/src/run.bat
index 4b7637563badda45b0f2f625dba1d185856cb75e..57a8828ef93eefc6928c2705d845441d574bdcbb 100644 (file)
--- a/src/run.bat
+++ b/src/run.bat
@@ -38,7 +38,7 @@ del env.bat
 echo.
 
 echo ##### Testing packages.
-go test std cmd -short -timeout=120s
+go test std cmd -short -timeout=240s
 if errorlevel 1 goto fail
 echo.
 
@@ -48,7 +48,7 @@ set OLDGOMAXPROCS=%GOMAXPROCS%
 :: creation of first goroutines and first garbage collections in the parallel setting.
 echo ##### GOMAXPROCS=2 runtime -cpu=1,2,4
 set GOMAXPROCS=2
-go test runtime -short -timeout=300s -cpu=1,2,4
+go test runtime -short -timeout=600s -cpu=1,2,4
 if errorlevel 1 goto fail
 echo.
 
@@ -56,7 +56,7 @@ set GOMAXPROCS=%OLDGOMAXPROCS%
 set OLDGOMAXPROCS=
 
 echo ##### sync -cpu=10
-go test sync -short -timeout=120s -cpu=10
+go test sync -short -timeout=240s -cpu=10
 if errorlevel 1 goto fail
 echo.