runtime/pprof: TestBlockProfile failures with "Bad chan … entry" or "Bad select … entry" #6999
Comments
Comment 1 by jphilbin@google.com: I realized that the failing test is in runtime/pprof and not in runtime/debug (that was the previous test that passed ok). There doesn't seem to be a way to edit issue titles once they're submitted? |
I've seen the same failure on the tip. changeset: 19174:f28dc1ba53cf tag: tip user: Rob Pike <r@golang.org> date: Wed Feb 19 15:01:50 2014 -0800 summary: cmd/pack: dump output of command of "go env" command in test uname -a Linux 3.8.0-35-generic #50-Ubuntu SMP Tue Dec 3 01:24:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux |
I currently see similar failures (ca. 1x/10 times). 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux 428dd5a62a9d tip ---- --- FAIL: TestBlockProfile (0.18s) pprof_test.go:370: Bad select send sync entry, expect: [0-9]+ [0-9]+ @ 0x[0-9,a-f]+ 0x[0-9,a-f]+ 0x[0-9,a-f]+ 0x[0-9,a-f]+ 0x[0-9,a-f]+ # 0x[0-9,a-f]+ runtime\.selectgo\+0x[0-9,a-f]+ .*/src/pkg/runtime/select.go:[0-9]+ # 0x[0-9,a-f]+ runtime/pprof_test\.blockSelectSendSync\+0x[0-9,a-f]+ .*/src/pkg/runtime/pprof/pprof_test.go:[0-9]+ # 0x[0-9,a-f]+ runtime/pprof_test\.TestBlockProfile\+0x[0-9,a-f]+ .*/src/pkg/runtime/pprof/pprof_test.go:[0-9]+ got: --- contention: cycles/second=2505600281 139908672 1 @ 0x4126e2 0x452c72 0x45230c 0x44b21b 0x42c3d0 # 0x4126e2 runtime.selectgo+0x12 /tmp2/go/src/pkg/runtime/select.go:183 # 0x452c72 runtime/pprof_test.blockSelectRecvAsync+0x152 /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:411 # 0x45230c runtime/pprof_test.TestBlockProfile+0x1ac /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:358 # 0x44b21b testing.tRunner+0x8b /tmp2/go/src/pkg/testing/testing.go:427 25348446 1 @ 0x47f552 0x452e7c 0x45230c 0x44b21b 0x42c3d0 # 0x47f552 sync.(*Mutex).Lock+0xd2 /tmp2/go/src/pkg/sync/mutex.go:66 # 0x452e7c runtime/pprof_test.blockMutex+0x7c /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:437 # 0x45230c runtime/pprof_test.TestBlockProfile+0x1ac /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:358 # 0x44b21b testing.tRunner+0x8b /tmp2/go/src/pkg/testing/testing.go:427 25318732 1 @ 0x47f1cd 0x452fae 0x45230c 0x44b21b 0x42c3d0 # 0x47f1cd sync.(*Cond).Wait+0x9d /tmp2/go/src/pkg/sync/cond.go:63 # 0x452fae runtime/pprof_test.blockCond+0x11e /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:450 # 0x45230c runtime/pprof_test.TestBlockProfile+0x1ac /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:358 # 0x44b21b testing.tRunner+0x8b /tmp2/go/src/pkg/testing/testing.go:427 25286875 1 @ 0x402f6b 0x452992 0x45230c 0x44b21b 0x42c3d0 # 0x402f6b runtime.chanrecv1+0x2b /tmp2/go/src/pkg/runtime/chan.go:308 # 0x452992 runtime/pprof_test.blockChanRecv+0xb2 /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:383 # 0x45230c runtime/pprof_test.TestBlockProfile+0x1ac /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:358 # 0x44b21b testing.tRunner+0x8b /tmp2/go/src/pkg/testing/testing.go:427 25279242 1 @ 0x402f6b 0x452b12 0x45230c 0x44b21b 0x42c3d0 # 0x402f6b runtime.chanrecv1+0x2b /tmp2/go/src/pkg/runtime/chan.go:308 # 0x452b12 runtime/pprof_test.blockChanClose+0xb2 /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:401 # 0x45230c runtime/pprof_test.TestBlockProfile+0x1ac /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:358 # 0x44b21b testing.tRunner+0x8b /tmp2/go/src/pkg/testing/testing.go:427 25268569 1 @ 0x402483 0x452a58 0x45230c 0x44b21b 0x42c3d0 # 0x402483 runtime.chansend1+0x43 /tmp2/go/src/pkg/runtime/chan.go:69 # 0x452a58 runtime/pprof_test.blockChanSend+0xb8 /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:392 # 0x45230c runtime/pprof_test.TestBlockProfile+0x1ac /tmp2/go/src/pkg/runtime/pprof/pprof_test.go:358 # 0x44b21b testing.tRunner+0x8b /tmp2/go/src/pkg/testing/testing.go:427 FAIL FAIL runtime/pprof 8.420s |
TestBlockProfile still fails w/ Bad mutex entry on tip (go1.7 devel). See https://storage.googleapis.com/go-build-log/88cc348c/freebsd-386-gce101_92f2a1f0.log
|
I can't find any instances of this bug on any of our builders going back 6 months. Closing as fixed. |
Ran clean.bash and all.bash in kvm with 2 cpu and 4 gb ram to build go1.13.6 using go1.12.12.
go version and go env after the build finished with above error:
|
@mikioh The original report was for a |
Filed |
@x448, I haven't been able to find any 2020-02-27T19:04:17-42f8199/darwin-arm64-mn4m2zdaios |
|
|
by jphilbin@google.com:
The text was updated successfully, but these errors were encountered: