[Bug 1110497] New: go test fails for multiple golang-* libraries

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1110497

            Bug ID: 1110497
           Summary: go test fails for multiple golang-* libraries
           Product: Fedora
           Version: rawhide
         Component: golang
          Assignee: vbatts(a)redhat.com
          Reporter: lsm5(a)redhat.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
                    lemenkov(a)gmail.com, lsm5(a)redhat.com,
                    renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com



Description of problem:

apparently, ever since the upgrade to go1.3rc2, go test in %check fails. 

Here's a sample from golang-github-gorilla-mux:

 go test github.com/gorilla/mux
/var/tmp/rpm-tmp.iEoDQJ: line 31: 10812 Segmentation fault     
GOPATH=/usr/share/gocode:/home/lsm5/repositories/pkgs/fedora/golang-github-gorilla-mux/BUILDROOT/golang-github-gorilla-mux-0-0.14.git136d54f.fc21.x86_64//usr/share/gocode
go test github.com/gorilla/mux
error: Bad exit status from /var/tmp/rpm-tmp.iEoDQJ (%check)


Version-Release number of selected component (if applicable): 1.3rc2-1.fc21


How reproducible: always


Steps to Reproduce:
1. install latest golang on rawhide
2. try rebuilding any previously built golang lib
(golang-github-gorilla-context or golang-github-gorilla-mux for instance)
3. see error

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1110497] go test fails for multiple golang-* libraries

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1110497

Vincent Batts <vbatts(a)redhat.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |RAWHIDE
        Last Closed|                            |2014-07-08 11:08:05



--- Comment #2 from Vincent Batts <vbatts(a)redhat.com&gt; ---
This test is no longer failing on the go1.3 release. Closing since that was a
release-candidate related issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.