Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime/pprof: cpuHog1 fails #9070

Closed
btracey opened this issue Nov 8, 2014 · 7 comments
Closed

runtime/pprof: cpuHog1 fails #9070

btracey opened this issue Nov 8, 2014 · 7 comments
Milestone

Comments

@btracey
Copy link
Contributor

btracey commented Nov 8, 2014

I tried installing the beta on a linux cluster for our group, and I get the error below.
I tried on tip (3:47 PST November 7th). The error persists in addition to a number of
panics in the GC. I output the last working version of go I had as well as go env. The
previous go version passed all of the tests, so it seems it's broken since then. I've
had problems in the past on this machine with clock asynchronisity, but they appear to
be synced up. I This is on CentOS and is part of a 8-node cluster. I am attempting to
compile go on the head node. The specific cpuHog test that fails is not consistent, nor
is the compilation failing at all. Please advise what I can do to help debug. 


ok      runtime/debug    0.006s
--- FAIL: TestCPUProfileMultithreaded (0.25s)
    pprof_test.go:165: runtime/pprof_test.cpuHog1: 49
    pprof_test.go:165: runtime/pprof_test.cpuHog2: 0
    pprof_test.go:179: runtime/pprof_test.cpuHog2 has 0 samples out of 49, want at least 1, ideally 24
FAIL
FAIL    runtime/pprof    20.165s
?       runtime/race    [no test files]


[btracey@zion go_tip]$ go version
go version devel +3d68989bd1ea Mon Oct 27 08:46:18 2014 -0700 linux/amd64

Go env output (from previous go installation):
GOARCH="amd64"
GOBIN=""
GOCHAR="6"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/ADL/btracey/mygo"
GORACE=""
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"



Failure on tip:
panic: runtime error: index out of range
fatal error: panic during gc

goroutine 1 [running, locked to thread]:
runtime.gothrow(0x62cd90, 0xf)
    /ADL/btracey/gover/go_tip/go/src/runtime/panic.go:503 +0x8e fp=0xc2082d9c58 sp=0xc2082d9c40
runtime.gopanic(0x5db6a0, 0xc208010010)
    /ADL/btracey/gover/go_tip/go/src/runtime/panic.go:343 +0x19d fp=0xc2082d9cc0 sp=0xc2082d9c58
runtime.panicindex()
    /ADL/btracey/gover/go_tip/go/src/runtime/panic.go:12 +0x4e fp=0xc2082d9ce8 sp=0xc2082d9cc0
runtime.(*traceStackDepot).dump(0x74a6f0)
    /ADL/btracey/gover/go_tip/go/src/runtime/trace.go:498 +0x1ef fp=0xc2082e9f30 sp=0xc2082d9ce8
runtime.TraceStop()
    /ADL/btracey/gover/go_tip/go/src/runtime/trace.go:173 +0x1d5 fp=0xc2082e9f88 sp=0xc2082e9f30
runtime.traceFinalize()
    /ADL/btracey/gover/go_tip/go/src/runtime/trace.go:89 +0x1b fp=0xc2082e9f90 sp=0xc2082e9f88
runtime.main()
    /ADL/btracey/gover/go_tip/go/src/runtime/proc.go:68 +0x105 fp=0xc2082e9fe0 sp=0xc2082e9f90
runtime.goexit()
    /ADL/btracey/gover/go_tip/go/src/runtime/asm_amd64.s:2232 +0x1 fp=0xc2082e9fe8 sp=0xc2082e9fe0

goroutine 563 [syscall]:
runtime_test.func·046(0x0, 0x4e94914f0000, 0x63ca30, 0x14, 0xc20804a060)
    /ADL/btracey/gover/go_tip/go/src/runtime/futex_test.go:47 +0x4d
created by runtime_test.TestFutexsleep
    /ADL/btracey/gover/go_tip/go/src/runtime/futex_test.go:51 +0x222

goroutine 564 [syscall]:
runtime_test.func·046(0x0, 0x1dcd65174876e800, 0x63c630, 0x13, 0xc20804a0c0)
    /ADL/btracey/gover/go_tip/go/src/runtime/futex_test.go:47 +0x4d
created by runtime_test.TestFutexsleep
    /ADL/btracey/gover/go_tip/go/src/runtime/futex_test.go:51 +0x222
@bradfitz
Copy link
Contributor

bradfitz commented Nov 8, 2014

Comment 1:

The test failure is in pprof, not debug. (note that the runtime/debug line has "ok"
before it)

@davecheney
Copy link
Contributor

Comment 2:

Status changed to WaitingForReply.

@davecheney
Copy link
Contributor

Comment 3:

Which kernel is this machine running ?

@ianlancetaylor
Copy link
Contributor

Comment 4:

Labels changed: added repo-main, release-go1.4.

@btracey
Copy link
Contributor Author

btracey commented Nov 8, 2014

Comment 5:

I have compiled 1_4_beta1 over a half a dozen times since the initial report, and cannot
reproduce the error again. Sorry for what seems to be a false report. The tip panic was
a fluke (residual from testing the trace recorder).

@ianlancetaylor
Copy link
Contributor

Comment 6:

Status changed to Retracted.

@javanthropus
Copy link

I just ran into this exact problem while attempting to build from the source distribution of version 1.4.2. The build was performed in a completely clean directory created by extracting the source archive. After seeing this issue, I deleted the directory, extracted the sources, and tried the build again and could not reproduce the issue.

Perhaps there is a race condition in the test?

@rsc rsc added this to the Go1.4 milestone Apr 14, 2015
@rsc rsc removed the release-go1.4 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants