release-3.4: updated test workflow go version to 1.16 #14134
Conversation
backport of release-3.5: etcd-io@6e800b9
…napshot tests. backport from release-3.5 etcd-io@74274f4
need newer version of bolt db for go1.16 compatibilty
PASSES='fmt bom dep' ./test auth/store.go:35:2: missing go.sum entry for module providing package golang.org/x/crypto/bcrypt (imported by go.etcd.io/etcd/auth); to add: go get go.etcd.io/etcd/auth /Users/bk/.gvm/pkgsets/go1.16.7/global/pkg/mod/github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0/client_metrics.go:7:2: missing go.sum entry for module providing package golang.org/x/net/context (imported by go.etcd.io/etcd/etcdserver/etcdserverpb); to add: go get go.etcd.io/etcd/etcdserver/etcdserverpb /Users/bk/.gvm/pkgsets/go1.16.7/global/pkg/mod/google.golang.org/grpc@v1.26.0/internal/transport/controlbuf.go:28:2: missing go.sum entry for module providing package golang.org/x/net/http2 (imported by go.etcd.io/etcd/proxy/httpproxy); to add: go get go.etcd.io/etcd/proxy/httpproxy /Users/bk/.gvm/pkgsets/go1.16.7/global/pkg/mod/google.golang.org/grpc@v1.26.0/internal/transport/controlbuf.go:29:2: missing go.sum entry for module providing package golang.org/x/net/http2/hpack (imported by github.com/soheilhy/cmux); to add: go get github.com/soheilhy/cmux@v0.1.4 /Users/bk/.gvm/pkgsets/go1.16.7/global/pkg/mod/google.golang.org/grpc@v1.26.0/server.go:36:2: missing go.sum entry for module providing package golang.org/x/net/trace (imported by go.etcd.io/etcd/embed); to add: go get go.etcd.io/etcd/embed
backport from branch-3.5: etcd-io#12200
|
I wasn't able to get a clean run of integration tests locally, there issues seams to be around watches and leases. |
|
The release of 3.4.19 is a priority to me now, but the first step is to make the pipeline green. But there are still some flaky failures, so the pipeline and test failures are still our top priority. If you or someone else has difficult on something, my generic suggestion is to either have a deep dive to get it resolved, or break down the PR to get the easier ones fixed firstly and do it step by step. If the task is a priority to me, then I may jump in to get it resolved by helping the contributor or fixing it myself. I was trying to help you to resolve this, but I did not do it because:
Sorry for the confusion. I will raise an issue to clearly state the plan for 3.4.19 on top of your issue 14105 or just add comments in your issue. Please feel free to continue to work on 3.4 per the plan by then. Thanks. |
No description provided.