-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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.
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
x/sys/unix: broken on Go 1.6 #26576
Comments
It seems |
…fetime Change-Id: I42e59149e58bd928d9beb2c6665ce186b377d2a1 Reviewed-on: https://go-review.googlesource.com/125640 Run-TryBot: Brad Fitzpatrick <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]>
Sorry, Go 1.6 is no longer supported. If you were using Go 1.6 for App Engine, note that GAE standard supports Go 1.9 (by default) now. |
What about other GCP client libraries? They were still building for golang 1.6 last time I checked: https://github.com/GoogleCloudPlatform/google-cloud-go/blob/master/.travis.yml |
Will no one rid of us of this meddlesome 1.6 release? |
I'm trying, Henry. My understanding was that GAE Standard was the last holdout and with it supporting Go 1.9 now we could move forward. I'd love to get confirmation on that. |
Not quite, Brad. There is a difference between supporting 1.9 and dropping support for 1.6. Please put this change behind a build tag. |
Sorry, let me be less snarky. Although 1.9 may be the GAE default, it is still possible to pin to other versions. We know that several projects pin to 1.6. Until an official deprecation policy is announced and implemented, we are obligated to support 1.6. |
It is already there I believe.
https://golang.org/doc/devel/release.html#policy. So "officially" 1.6 is no longer supported. |
Sorry, @agnivade, I was referring to App Engine, not Go. |
@jba, do we have that documented somewhere? Let's agree on something and write something down. We can't have some invisible policy that non-Google Go contributors don't know about. Please document somewhere what's expected of the Go App Engine libraries and what's expected of the Go libraries (and which). And for which environments. (Standard? Flex? Go 1.6 only? which packages?) Also, we have no build & test infrastructure setup for older releases anymore. You never replied to #26302 either, which is about removing Go 1.8 and older support in x/net/http2, which has become a mess of +build tags and files: https://github.com/golang/net/tree/master/http2 ... such messes hinder development. It's just not sustainable to keep supporting Go 1.6. Perhaps y'all need to vendor old copies of certain golang.org/x/* packages to keep App Engine libraries working, if that's what you've promised. But I'm not sure what the constraints are. Please document it somewhere. Once we see & agree upon a policy, then we can move forward with this bug. |
Vendoring is the only reasonable solution here. It isn't sustainable to support so many versions of Go. If App Engine was not a Google product, I know what we would do. |
Vendoring doesn't work on App Engine, unfortunately. |
@jba, maybe not with cmd/go's special handling of "vendor" directories, but it works in the general sense: you can copy files from your dependencies into your own GOPATH and manage your own whole GOPATH (your app + your deps) in your VCS. |
This can be reverted when golang/go#26576 is resolved.
So, what's the way forward here. As it is several builds remain broken: https://travis-ci.org/GoogleCloudPlatform/google-cloud-go It seems GRPC team disabled the 1.6 CI builds. Is that a reasonable temporary workaround? |
golang/x/sys/unix removed support for Go 1.6. Decision on our side pending discussion in golang/go#26576. Disable the E2E test for now to avoid covering other failures. Change-Id: I47fabb89c0ccc5f9e7bef5502bcd71fd3e2b586a Reviewed-on: https://code-review.googlesource.com/30910 Reviewed-by: kokoro <[email protected]> Reviewed-by: Jonathan Amsterdam <[email protected]> Reviewed-by: Alexey Alexandrov <[email protected]>
I think the only other choice would be to pin your dependencies to versions that support 1.6 in your 1.6 CI build. I.e. |
Or get rid of x/sys dependency?
…On Thu, Jul 26, 2018 at 11:12 AM dfawley ***@***.***> wrote:
It seems GRPC team disabled the 1.6 CI builds. Is that a reasonable
temporary workaround?
I think the only other choice would be to pin your dependencies to
versions that support 1.6 in your 1.6 CI build. I.e. cd ...../
golang.org/x/sys && git checkout e072cad~1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#26576 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABctwBDYePiSA0M53bMm_gJrLv9p41O5ks5uKgaSgaJpZM4VfBvk>
.
--
Alex
|
|
|
@dfawley, can |
I think it should be fine, but this sounds like kicking the can down the road to me. When will our next dependency break support for Go 1.6? |
ChannelZ is a debugging feature in grpc. It has not had appengine support; this commit removes its support for 1.6, too. This change is because in a recent sys/unix commit 1.6 support was broken. See: golang/go#26576 (comment).
ChannelZ is a debugging feature in grpc. It has not had appengine support; this commit removes its support for 1.6, too. This change is because in a recent sys/unix commit 1.6 support was broken. See: golang/go#26576 (comment).
ChannelZ is a debugging feature in grpc. It has not had appengine support; this commit removes its support for 1.6, too. This change is because in a recent sys/unix commit 1.6 support was broken. See: golang/go#26576 (comment).
ChannelZ is a debugging feature in grpc. It has not had appengine support; this commit removes its support for 1.6, too. This change is because in a recent sys/unix commit 1.6 support was broken. See: golang/go#26576 (comment).
ChannelZ is a debugging feature in grpc. It has not had appengine support; this commit removes its support for 1.6, too. This change is because in a recent sys/unix commit 1.6 support was broken. See: golang/go#26576 (comment).
ChannelZ is a debugging feature in grpc. It has not had appengine support; this commit removes its support for 1.6, too. This change is because in a recent sys/unix commit 1.6 support was broken. See: golang/go#26576 (comment).
ChannelZ is a debugging feature in grpc. It has not had appengine support; this commit removes its support for 1.6, too. This change is because in a recent sys/unix commit 1.6 support was broken. See: golang/go#26576 (comment).
Uh... sorry for the commit spam. Apparently amending + |
@hiranya911 We've put the 1.6-incompatible code behind build flags in grpc (which google-cloud-go Firestore client uses): grpc/grpc-go#2242. You should now be able to use our GCP clients in 1.6 again. Let me know if that's not the case. |
@jadekler that indeed fixes the issue for us. Much appreciated 👍 https://travis-ci.org/firebase/firebase-admin-go/jobs/407811247 |
The Google stuff broken by this was fixed, so closing this issue. The Go project itself has no plans to change our support policy to support things older than the past two releases. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.6.4 linux/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
Some of our CI builds on Go 1.6 suddenly started failing (builds are successful on other Go version)
Issue seems to have been caused by golang/sys@e072cad
The text was updated successfully, but these errors were encountered: