-
Notifications
You must be signed in to change notification settings - Fork 18.8k
Description
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.7.5 and 1.8.3
What operating system and processor architecture are you using (go env)?
linux, amd64
What did you do?
I am using go1.7 to bootstrap go1.8, install from source, since my system RHEL 5.x not supported by Go distribution
All my go env setting:
GOROOT=${golang_dir}/go
GOROOT_BOOTSTRAP="/opt/elasticbeanstalk/lib/go"
GOROOT_FINAL="/opt/elasticbeanstalk/lib/go"
GOOS="linux"
GOARCH="amd64"
# GO_TEST_TIMEOUT_SCALE=10
# CONFIG_HIGH_RES_TIMERS=y
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOPATH="/root/go"
GORACE=""
GOTOOLDIR="/opt/elasticbeanstalk/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build933756113=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
I think those env-variables are correct since it could be successfully installed. But in my install-golang-script, it will roughly 30% fail, after I run ./all.bash.
All of the fail is in testing packages stage due to
*** Test killed with quit: ran too long (4m0s).
FAIL runtime/pprof 240.050s
I tried to set timeout longer, like this:
export GO_TEST_TIMEOUT_SCALE=10,
but the result is it will stuck at this stage, and it will not exit even more than 10 minutes.
I also tried to set high resolution timer, but still didn't work.
export CONFIG_HIGH_RES_TIMERS=y
I used top to check the running process information like this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
31799 root 20 0 119m 110m 2488 S 100.7 0.4 5:51.92 pprof.test
I set a cronjob to install every 10mins for testing, and it needs around 7mins to build. If it is successful, there will be a time-stamp in my log file.
The results are shown as follow.
Sat Jul 22 02:46:22 UTC 2017
Sat Jul 22 03:27:20 UTC 2017
Sat Jul 22 03:46:55 UTC 2017
Sat Jul 22 03:56:44 UTC 2017
Sat Jul 22 04:06:32 UTC 2017
Sat Jul 22 04:16:13 UTC 2017
Sat Jul 22 04:26:16 UTC 2017
Sat Jul 22 04:46:47 UTC 2017
Sat Jul 22 04:56:49 UTC 2017
Sat Jul 22 05:16:45 UTC 2017
Sat Jul 22 05:26:50 UTC 2017
Sat Jul 22 05:57:17 UTC 2017
Sat Jul 22 06:27:19 UTC 2017
Sat Jul 22 06:37:02 UTC 2017
Sat Jul 22 07:07:15 UTC 2017
Sat Jul 22 07:17:00 UTC 2017
Sat Jul 22 07:36:48 UTC 2017
Anyone know how to fix it?
Update: when I use a new amazon ec2 instance, and the first-time install go from source will always success. So does I restart the instance (considering as running new one).
Fail will randomly occur since the 1st time install, no mater it is running using my own script in crontab or manually run it.
UpdateUpdate Using at command to set scheduled task to install it will always Failed: exit status 1 due to the same reason.