aboutsummaryrefslogtreecommitdiff
path: root/src/run.bat
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2015-02-28 17:23:32 -0500
committerRuss Cox <rsc@golang.org>2015-03-01 00:38:53 +0000
commit0aac9bb82d9cbc34fa723fc653c6659ed48da772 (patch)
tree59f644310459a85c2b14b7b360fd65326248a85a /src/run.bat
parent4734464a140b997fd85b636a66bfa6cd1079e0a1 (diff)
downloadgo-0aac9bb82d9cbc34fa723fc653c6659ed48da772.tar.gz
go-0aac9bb82d9cbc34fa723fc653c6659ed48da772.zip
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>
Diffstat (limited to 'src/run.bat')
-rw-r--r--src/run.bat6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/run.bat b/src/run.bat
index 4b7637563b..57a8828ef9 100644
--- 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.