Bug 1437223

Summary: golang is FTBFS in F26
Product: [Fedora] Fedora Reporter: Stephen Gallagher <sgallagh>
Component: golangAssignee: Vincent Batts <vbatts>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 26CC: admiller, amurdaca, golang-updates, jcajka, lemenkov, mmathesi, psabata, renich, s, vbatts
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-30 08:12:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1400162    

Description Stephen Gallagher 2017-03-29 19:58:39 UTC
Description of problem:
Attempting to build golang-1.8-2.fc26 on the current F26 buildroot results in consistent failure in one of the tests

Version-Release number of selected component (if applicable):
golang-1.8-2.fc26

How reproducible:
Every time

Steps to Reproduce:
1. fedpkg clone golang
2. fedpkg srpm
3. koji build --scratch --arch=x86_64 rawhide golang-1.8-2.fc26.src.rpm

Actual results:
##### API check
# go tool dist test -run=^api$
/builddir/build/BUILD/go/test/runtest.exe --shard=3 --shards=5
/builddir/build/BUILD/go/test/runtest.exe --shard=4 --shards=5
go run /builddir/build/BUILD/go/src/cmd/api/run.go
Go version is "go1.8", ignoring -next /builddir/build/BUILD/go/api/next.txt
FAILED
error: Bad exit status from /var/tmp/rpm-tmp.tSF8Ww (%check)
RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.tSF8Ww (%check)
Child return code was: 1

Expected results:

Successful build

Additional info:
Failed scratch-build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=18667239

Comment 1 Jakub Čajka 2017-03-30 08:12:25 UTC

*** This bug has been marked as a duplicate of bug 1437101 ***