Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1437223 - golang is FTBFS in F26
Summary: golang is FTBFS in F26
Status: CLOSED DUPLICATE of bug 1437101
Alias: None
Product: Fedora
Classification: Fedora
Component: golang
Version: 26
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Vincent Batts
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: BaseRuntimeFTBFS
TreeView+ depends on / blocked
Reported: 2017-03-29 19:58 UTC by Stephen Gallagher
Modified: 2017-03-30 08:12 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-03-30 08:12:25 UTC
Type: Bug

Attachments (Terms of Use)

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):

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
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:

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

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

Note You need to log in before you can comment on or make changes to this bug.