juju-core

fatal error running test suite on arm64

Bug #1287879 reported by Curtis Hovey on 2014-03-04

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	juju-core	Fix Released	Medium	Unassigned
	gccgo-go (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

The following was seen running the juju-core unittests on an arm64 instance. I substituted "gccgo-4.9 gccgo-go" for golang and "juju-mongodb" for mongodb-server

$ make check
go test launchpad.net/juju-core/...
ok launchpad.net/juju-core 11.164s
unexpected fault address 0x3e80000167b
fatal error: fault
[signal 0xb code=0x1 addr=0x3e80000167b]

goroutine 8 [running]:

:0
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 1 [semacquire]:
main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:744
main.runTest
/build/buildd/gccgo-go-1.2/src/cmd/go/test.go:508
main.main
/build/buildd/gccgo-go-1.2/src/cmd/go/main.go:161

goroutine 3 [syscall]:
goroutine in C code; stack unavailable

goroutine 5 [syscall]:
goroutine in C code; stack unavailable
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 6 [syscall]:
goroutine in C code; stack unavailable
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 7 [syscall]:
goroutine in C code; stack unavailable
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 9 [syscall]:
goroutine in C code; stack unavailable
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 10 [syscall]:
goroutine in C code; stack unavailable
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 11 [syscall]:
goroutine in C code; stack unavailable
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 12 [syscall]:
goroutine in C code; stack unavailable
created by main.do.pN12_main.builder
/build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722

goroutine 246 [syscall]:
goroutine in C code; stack unavailable

goroutine 213 [syscall]:
goroutine in C code; stack unavailable

goroutine 240 [syscall]:
goroutine in C code; stack unavailable

goroutine 255 [syscall]:
goroutine in C code; stack unavailable

goroutine 235 [syscall]:
goroutine in C code; stack unavailable

goroutine 251 [syscall]:
goroutine in C code; stack unavailable

goroutine 256 [runnable]:

goroutine 33 [runnable]:

goroutine 94 [chan receive]:
main.$nested29
/build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:21
created by main.processSignals
/build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:20

goroutine 254 [syscall]:
goroutine in C code; stack unavailable
make: *** [check] Error 2

See original description

Tags:

Curtis Hovey (sinzui) on 2014-03-04

Changed in juju-core:
milestone:	none → 2.0

Revision history for this message

Dave Cheney (dave-cheney) wrote on 2014-03-04: Re: [Bug 1287879] [NEW] fatal error running test suite on arm64

Download full text (6.7 KiB)

looks like the /usr/bin/go process died, not the test it was running.

please add the gccgo-go project to this bug report.

On Wed, Mar 5, 2014 at 7:00 AM, Curtis Hovey <email address hidden> wrote:
> Public bug reported:
>
> The following was seen running the juju-core unittests on an arm64
> instance. The I substituted "gccgo-4.9 gccgo-go" for golang and "juju-
> mongodb" for mongodb-server
>
> $ make check
> go test launchpad.net/juju-core/...
> ok launchpad.net/juju-core 11.164s
> unexpected fault address 0x3e80000167b
> fatal error: fault
> [signal 0xb code=0x1 addr=0x3e80000167b]
>
> goroutine 8 [running]:
>
> :0
>
> :0
>
> :0
>
> :0
>
> :0
>
> :0
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 1 [semacquire]:
> main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:744
> main.runTest
> /build/buildd/gccgo-go-1.2/src/cmd/go/test.go:508
> main.main
> /build/buildd/gccgo-go-1.2/src/cmd/go/main.go:161
>
> goroutine 3 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 5 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 6 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 7 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 9 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 10 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 11 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 12 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 246 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 213 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 240 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 255 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 235 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 251 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 256 [runnable]:
>
> goroutine 33 [runnable]:
>
> goroutine 94 [chan receive]:
> main.$nested29
> /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:21
> created by main.processSignals
> /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:20
>
> goroutine 254 [syscall]:
> goroutine in C code; stack unavailabl...

looks like the /usr/bin/go process died, not the test it was running.

please add the gccgo-go project to this bug report.

On Wed, Mar 5, 2014 at 7:00 AM, Curtis Hovey <curtis@canonical.com> wrote:
> Public bug reported:
>
> The following was seen running the juju-core unittests on an arm64
> instance. The I substituted "gccgo-4.9 gccgo-go" for golang and "juju-
> mongodb" for mongodb-server
>
> $ make check
> go test launchpad.net/juju-core/...
> ok      launchpad.net/juju-core 11.164s
> unexpected fault address 0x3e80000167b
> fatal error: fault
> [signal 0xb code=0x1 addr=0x3e80000167b]
>
> goroutine 8 [running]:
>
>         :0
>
>         :0
>
>         :0
>
>         :0
>
>         :0
>
>         :0
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 1 [semacquire]:
> main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:744
> main.runTest
>         /build/buildd/gccgo-go-1.2/src/cmd/go/test.go:508
> main.main
>         /build/buildd/gccgo-go-1.2/src/cmd/go/main.go:161
>
> goroutine 3 [syscall]:
>         goroutine in C code; stack unavailable
>
> goroutine 5 [syscall]:
>         goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 6 [syscall]:
>         goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 7 [syscall]:
>         goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 9 [syscall]:
>         goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 10 [syscall]:
>         goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 11 [syscall]:
>         goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 12 [syscall]:
>         goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 246 [syscall]:
>         goroutine in C code; stack unavailable
>
> goroutine 213 [syscall]:
>         goroutine in C code; stack unavailable
>
> goroutine 240 [syscall]:
>         goroutine in C code; stack unavailable
>
> goroutine 255 [syscall]:
>         goroutine in C code; stack unavailable
>
> goroutine 235 [syscall]:
>         goroutine in C code; stack unavailable
>
> goroutine 251 [syscall]:
>         goroutine in C code; stack unavailable
>
> goroutine 256 [runnable]:
>
> goroutine 33 [runnable]:
>
> goroutine 94 [chan receive]:
> main.$nested29
>         /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:21
> created by main.processSignals
>         /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:20
>
> goroutine 254 [syscall]:
>         goroutine in C code; stack unavailable
> make: *** [check] Error 2
>
> ** Affects: juju-core
>      Importance: High
>          Status: Triaged
>
>
> ** Tags: arm64 test-failure
>
> ** Changed in: juju-core
>     Milestone: None => 2.0
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1287879
>
> Title:
>   fatal error running test suite on arm64
>
> Status in juju-core:
>   Triaged
>
> Bug description:
>   The following was seen running the juju-core unittests on an arm64
>   instance. The I substituted "gccgo-4.9 gccgo-go" for golang and "juju-
>   mongodb" for mongodb-server
>
>   $ make check
>   go test launchpad.net/juju-core/...
>   ok    launchpad.net/juju-core 11.164s
>   unexpected fault address 0x3e80000167b
>   fatal error: fault
>   [signal 0xb code=0x1 addr=0x3e80000167b]
>
>   goroutine 8 [running]:
>
>           :0
>
>           :0
>
>           :0
>
>           :0
>
>           :0
>
>         :0
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 1 [semacquire]:
>   main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:744
>   main.runTest
>         /build/buildd/gccgo-go-1.2/src/cmd/go/test.go:508
>   main.main
>         /build/buildd/gccgo-go-1.2/src/cmd/go/main.go:161
>
>   goroutine 3 [syscall]:
>         goroutine in C code; stack unavailable
>
>   goroutine 5 [syscall]:
>         goroutine in C code; stack unavailable
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 6 [syscall]:
>         goroutine in C code; stack unavailable
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 7 [syscall]:
>         goroutine in C code; stack unavailable
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 9 [syscall]:
>         goroutine in C code; stack unavailable
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 10 [syscall]:
>         goroutine in C code; stack unavailable
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 11 [syscall]:
>         goroutine in C code; stack unavailable
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 12 [syscall]:
>         goroutine in C code; stack unavailable
>   created by main.do.pN12_main.builder
>         /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
>   goroutine 246 [syscall]:
>         goroutine in C code; stack unavailable
>
>   goroutine 213 [syscall]:
>         goroutine in C code; stack unavailable
>
>   goroutine 240 [syscall]:
>         goroutine in C code; stack unavailable
>
>   goroutine 255 [syscall]:
>         goroutine in C code; stack unavailable
>
>   goroutine 235 [syscall]:
>         goroutine in C code; stack unavailable
>
>   goroutine 251 [syscall]:
>         goroutine in C code; stack unavailable
>
>   goroutine 256 [runnable]:
>
>   goroutine 33 [runnable]:
>
>   goroutine 94 [chan receive]:
>   main.$nested29
>         /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:21
>   created by main.processSignals
>         /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:20
>
>   goroutine 254 [syscall]:
>         goroutine in C code; stack unavailable
>   make: *** [check] Error 2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1287879/+subscriptions

Curtis Hovey (sinzui) on 2014-03-04

tags:

added: ci

Curtis Hovey (sinzui) on 2014-03-04

description:

updated

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2014-03-31:

Hi, this looks like this bug: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1279620. I'll be posting libc debs to try with soon.

Revision history for this message

Dave Cheney (dave-cheney) wrote on 2014-03-31: Re: [Bug 1287879] Re: fatal error running test suite on arm64

Download full text (3.5 KiB)

Awesome!

On Mon, Mar 31, 2014 at 12:54 PM, Michael Hudson-Doyle
<email address hidden> wrote:
> Hi, this looks like this bug:
> https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1279620. I'll be
> posting libc debs to try with soon.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1287879
>
> Title:
> fatal error running test suite on arm64
>
> Status in juju-core:
> Triaged
> Status in "gccgo-go" package in Ubuntu:
> New
>
> Bug description:
> The following was seen running the juju-core unittests on an arm64
> instance. I substituted "gccgo-4.9 gccgo-go" for golang and "juju-
> mongodb" for mongodb-server
>
> $ make check
> go test launchpad.net/juju-core/...
> ok launchpad.net/juju-core 11.164s
> unexpected fault address 0x3e80000167b
> fatal error: fault
> [signal 0xb code=0x1 addr=0x3e80000167b]
>
> goroutine 8 [running]:
>
> :0
>
> :0
>
> :0
>
> :0
>
> :0
>
> :0
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 1 [semacquire]:
> main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:744
> main.runTest
> /build/buildd/gccgo-go-1.2/src/cmd/go/test.go:508
> main.main
> /build/buildd/gccgo-go-1.2/src/cmd/go/main.go:161
>
> goroutine 3 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 5 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 6 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 7 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 9 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 10 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 11 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 12 [syscall]:
> goroutine in C code; stack unavailable
> created by main.do.pN12_main.builder
> /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722
>
> goroutine 246 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 213 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 240 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 255 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 235 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 251 [syscall]:
> goroutine in C code; stack unavailable
>
> goroutine 256 [runnable]:
>
> goroutine 33 [runnable]:
>
> ...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Changed in gccgo-go (Ubuntu):
status:	New → Incomplete
status:	Incomplete → Fix Released