Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/build: netbsd-386 builds at go1.8 use a broken go binary #23102

Closed
bsiegert opened this issue Dec 12, 2017 · 3 comments
Closed

x/build: netbsd-386 builds at go1.8 use a broken go binary #23102

bsiegert opened this issue Dec 12, 2017 · 3 comments
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge
Milestone
Unreleased

Comments

@bsiegert
Copy link
Contributor

The "Sub-repositories at release-branch.go1.8" column for netbsd-386 is all red. The error is always

go list error:

tests failed: fork/exec /tmp/workdir/go/bin/go: exec format error

This indicates that there is a broken go binary that is being used. Does that builder compile go1.8 from scratch?
@bradfitz bradfitz changed the title netbsd-386 builds at go1.8 use a broken go binary x/build: netbsd-386 builds at go1.8 use a broken go binary Dec 12, 2017
@gopherbot gopherbot added this to the Unreleased milestone Dec 12, 2017
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Dec 12, 2017
@bradfitz
Copy link
Contributor

Does that builder compile go1.8 from scratch?

If needed. If it's already built, it uses a cached version.

I'll just disable netbsd-* for Go 1.8. And maybe even Go 1.9, even though it's passing. It's kinda a waste of resources.

@gopherbot
Copy link

Change https://golang.org/cl/83536 mentions this issue: app: return the name of the Go branch in the JSON state of subrepos

gopherbot pushed a commit to golang/build that referenced this issue Dec 12, 2017
@bradfitz
app: return the name of the Go branch in the JSON state of subrepos
f4148b5 
We want to pass this down to the coordinator so each
dashboard.BuildConfig can have its own policy on which branches to
build. For example, we'll have NetBSD skip building subrepos for Go
versions that are too old.

Updates golang/go#23102

Change-Id: I40d35c9c5a6d4455772430c169dbea054929545e
Reviewed-on: https://go-review.googlesource.com/83536
Reviewed-by: Andrew Bonventre <andybons@golang.org>
@gopherbot
Copy link

Change https://golang.org/cl/83576 mentions this issue: cmd/coordinator: don't test subreops on NetBSD for Go 1.8 and Go 1.9

@golang golang locked and limited conversation to collaborators Dec 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@bradfitz @bsiegert @gopherbot