I'm finding that on my laptop the cmd/go tests sometimes time out when
the laptop is heavily loaded because I'm running all the tests in
parallel. The cmd/go tests are really a whole testsuite, not a single
test. So bumping the timeout. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
2018-02-09 Ian Lance Taylor <i...@golang.org>
* Makefile.am (GOTOOLS_TEST_TIMEOUT): Double value.
Index: Makefile.am
===================================================================
--- Makefile.am (revision 257494)
+++ Makefile.am (working copy)
@@ -162,7 +162,7 @@ uninstall-local:
GOTESTFLAGS =
# Number of seconds before tests time out.
-GOTOOLS_TEST_TIMEOUT = 240
+GOTOOLS_TEST_TIMEOUT = 480
# Run tests using the go tool, and frob the output to look like that
# generated by DejaGNU. The main output of this is two files:
Index: Makefile.in
===================================================================
--- Makefile.in (revision 257494)
+++ Makefile.in (working copy)
@@ -348,7 +348,7 @@ MOSTLYCLEANFILES = \
@NATIVE_TRUE@GOTESTFLAGS =
# Number of seconds before tests time out.
-@NATIVE_TRUE@GOTOOLS_TEST_TIMEOUT = 240
+@NATIVE_TRUE@GOTOOLS_TEST_TIMEOUT = 480
# CHECK_ENV sets up the environment to run the newly built go tool.
# If you change this, change ECHO_ENV, below.
@@ -635,8 +635,8 @@ distclean-generic:
maintainer-clean-generic:
@echo "This command is intended for maintainers to use"
@echo "it deletes files that may require special tools to rebuild."
-@NATIVE_FALSE@install-exec-local:
@NATIVE_FALSE@uninstall-local:
+@NATIVE_FALSE@install-exec-local:
clean: clean-am
clean-am: clean-binPROGRAMS clean-generic clean-noinstPROGRAMS \
