** Changed in: gccgo-go (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393825
Title:
Juju testsuite fails in random ways
To manage notifications abou
gccgo-go is removed in vivid, superseded by gccgo-5
** Also affects: gccgo-go (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: gccgo-go (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: gccgo-go (Ubuntu)
Status: Confirmed => Invalid
-
The stilson machines that run the tests have 9.8G RAM. They always have.
** Changed in: gccgo-go (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393825
Dave has done some testing, and we are pretty sure that this is due to
lack of memory. Can you confirm please the amount of memory on the
machine or VM running these tests, and the memory use of the test
process?
We were not able to reproduce these problems on a VM running with 8gig
or ram.
** C
It turns out the vivid package does not yet have the needed patch from
https://go-review.googlesource.com/#/c/1840/ we'll have to wait for an
upstream release I guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Related bug 1417771. Let's release an updated version of gccgo-go for
trusty at least, if not precise. In vivid, a more recent release
(1.2.1-0ubuntu7 ) has the fix.
** Changed in: gccgo-go (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
** Changed in: gccgo-go (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393825
Title:
Juju testsuite fails in random ways
To manage notifications about th
I filed a bug in the gcc tracker about this
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64001).
** Bug watch added: GCC Bugzilla #64001
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Another part of this is from a panic in a later test:
ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/&& go test
./... -compiler gccgo -v -gocheck.v
-gocheck.f=TestStartInstanceWithUnknownAZError)
3
=== RUN Test
---
After a bit more poking I am still pretty confused, but (a) it seems to
do with stack splitting, so won't affect the platforms we actually care
about gccgo on (b) it doesn't happen with gcc mainline so it's probably
a bug that's fixed upstream. So I'm not sure it's worth spending a heap
of time on
The HTTPS side of this I can reproduce (inconsistently) running just one
test:
ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/&& go test
./... -compiler gccgo -v -gocheck.v -gocheck.f=TestMustDisableSSLVerify)
3
=== RUN Test
unexpected fault address 0x7f6b0011
fatal error: fa
The crash is happening during stack splitting. The immediate cause for
the crash is that the stack pointer is totally bogus, presumably because
the function that is supposed to return an address to use as the new
stack segment returned something bogus. I don't really see how that is
possible (but
** Description changed:
Two parts of the juju-core test suite panic or segfault when run with
-compiler gccgo on amd64.
Some examples, in provider/openstack:
ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/&& go test
./... -compiler gccgo -gocheck.v -v)
3
=== RUN
This is the gdb traceback seen while running the openstack provider
tests: http://pastebin.ubuntu.com/9073749/
Funnily enough I saw a traceback very much like this just yesterday.
What I know at this point:
It's failing while parsing a https certificate. The failure occurs
during allocation: go
14 matches
Mail list logo
