Details
Test Blocker Description
I was running volume tests on 5.5.0-2562 which had updated manifest to use the latest gocb/gocbcore changes(see MB-29147 ). Function deployment failed with the following panic.
panic: runtime error: index out of range
|
|
|
goroutine 474 [running]:
|
panic(0xc54dc0, 0xc420018100)
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/panic.go:500 +0x1a1 fp=0xc426331d90 sp=0xc426331d00
|
runtime.panicindex()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/panic.go:27 +0x6d fp=0xc426331dc0 sp=0xc426331d90
|
gopkg.in/couchbase/gocbcore%2ev7.(*Agent).GetEx.func1(0xc420681290, 0xc42022a5a0, 0x0, 0x0)
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/godeps/src/gopkg.in/couchbase/gocbcore.v7/agentops_crud.go:40 +0x161 fp=0xc426331e00 sp=0xc426331dc0
|
gopkg.in/couchbase/gocbcore%2ev7.(*memdQRequest).tryCallback(0xc42022a5a0, 0xc420681290, 0x0, 0x0, 0x2)
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdqpackets.go:76 +0xe6 fp=0xc426331e30 sp=0xc426331e00
|
gopkg.in/couchbase/gocbcore%2ev7.(*memdClient).resolveRequest(0xc4200b18c0, 0xc420681290)
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdclient.go:180 +0x26f fp=0xc426331ed8 sp=0xc426331e30
|
gopkg.in/couchbase/gocbcore%2ev7.(*memdClient).run.func2(0xc4200b18c0, 0xc421f22780, 0xc421f227e0, 0xc421f22840)
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdclient.go:250 +0x2d0 fp=0xc426331f90 sp=0xc426331ed8
|
runtime.goexit()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc426331f98 sp=0xc426331f90
|
created by gopkg.in/couchbase/gocbcore%2ev7.(*memdClient).run
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/godeps/src/gopkg.in/couchbase/gocbcore.v7/memdclient.go:268 +0x105
|
|
|
goroutine 1 [chan receive]:
|
runtime.gopark(0xe0cbd0, 0xc42134e298, 0xd6e52d, 0xc, 0x47f717, 0x3)
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/proc.go:259 +0x13a fp=0xc420433660 sp=0xc420433630
|
runtime.goparkunlock(0xc42134e298, 0xd6e52d, 0xc, 0x17, 0x3)
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/proc.go:265 +0x5e fp=0xc4204336a0 sp=0xc420433660
|
runtime.chanrecv(0xc06fe0, 0xc42134e240, 0x0, 0x1, 0x4)
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/chan.go:496 +0x2df fp=0xc420433728 sp=0xc4204336a0
|
runtime.chanrecv1(0xc06fe0, 0xc42134e240, 0x0)
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/chan.go:378 +0x35 fp=0xc420433760 sp=0xc420433728
|
github.com/couchbase/eventing/consumer.(*Consumer).SignalBootstrapFinish(0xc420398900)
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/goproj/src/github.com/couchbase/eventing/consumer/exported_functions.go:266 +0x1ce fp=0xc4204337f0 sp=0xc420433760
|
github.com/couchbase/eventing/producer.(*Producer).SignalBootstrapFinish(0xc4201ce380)
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/goproj/src/github.com/couchbase/eventing/producer/exported_functions.go:247 +0x352 fp=0xc4204338e0 sp=0xc4204337f0
|
github.com/couchbase/eventing/supervisor.(*SuperSupervisor).HandleSupCmdMsg(0xc4203ba1a0)
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/goproj/src/github.com/couchbase/eventing/supervisor/super_supervisor.go:617 +0x13af fp=0xc420433e50 sp=0xc4204338e0
|
main.main()
|
/home/couchbase/jenkins/workspace/couchbase-server-unix/goproj/src/github.com/couchbase/eventing/cmd/producer/main.go:77 +0x252 fp=0xc420433f48 sp=0xc420433e50
|
runtime.main()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/proc.go:183 +0x1f4 fp=0xc420433fa0 sp=0xc420433f48
|
runtime.goexit()
|
/home/couchbase/.cbdepscache/exploded/x86_64/go-1.7.6/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc420433fa8 sp=0xc420433fa0
|
I have attached logs from all the eventing nodes. Abhishek Singh - Please reassign it to SDK team with your analysis if you think this is because of latest gocb/gocbcore changes. I don't see the same panic in 5.5.0-2556 which is our weekly build which doesn't have the latest gocb/gocbcore changes.
