[release/1.4] Update Go to 1.16.14

[thaJeztah]

Update Go to 1.16.14

Includes security fixes for crypto/elliptic (CVE-2022-23806), math/big (CVE-2022-23772),
and cmd/go (CVE-2022-23773).

go1.16.14 (released 2022-02-10) includes security fixes to the crypto/elliptic,
math/big packages and to the go command, as well as bug fixes to the compiler,
linker, runtime, the go command, and the debug/macho, debug/pe, net/http/httptest,
and testing packages. See the Go 1.16.14 milestone on our issue tracker for details:

https://github.com/golang/go/issues?q=milestone%3AGo1.16.14+label%3ACherryPickApproved

full diff: golang/go@go1.16.13...go1.16.14

Update Go to 1.16.13

go1.16.13 (released 2022-01-06) includes fixes to the compiler, linker, runtime,
and the net/http package. See the Go 1.16.13 milestone on our issue tracker for
details:

https://github.com/golang/go/issues?q=milestone%3AGo1.16.13+label%3ACherryPickApproved

[thaJeztah]

Not sure if there's gonna be more 1.4.x release, but if so, we may as well have the branch up to date

[estesp]

Just FYI, something has gotten stale on release/1.4 where the ginko/CRI tests no longer work. I tried to dig into it a bit last week and dead ended after finding the same commits are being used elsewhere. Might need someone more versed in the critest project to help figure it out.

[thaJeztah]

Ah, I see it indeed;

ginkgo run failed
    default:   flag provided but not defined: -skipMeasurements

It guess it goes wrong here (as no version is specified);

containerd/script/setup/install-critools

Line 23 in 18a2715

go get -u github.com/onsi/ginkgo/ginkgo

Possibly something like 6b0e241 would be needed (trying to cherry-pick it, but doesn't apply clean)

[theopenlab-ci]

Build succeeded.

• containerd-build-arm64 : NODE_FAILURE in 0s (non-voting)

[thaJeztah]

Pushed a commit, roughly based on 6b0e241 (#6328); let's see if that fixes it.

Did a quick check, and ginkgo 1.16.5 looks to still have that flag;

go install github.com/onsi/ginkgo/ginkgo@v1.16.5
#...

ginkgo --help | grep skipMeasurements
  -skipMeasurements

[theopenlab-ci]

Build succeeded.

• containerd-build-arm64 : NODE_FAILURE in 0s (non-voting)

[thaJeztah]

Hmm... now it looks to be failing in vagrant provisioning

==> default: Running provisioner: install-cri-tools (shell)...
    default: Running: inline script
    default: + /root/go/src/github.com/containerd/containerd/script/setup/install-critools
    default: go: modules disabled by GO111MODULE=off; see 'go help modules'
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what

[thaJeztah]

Arf.. by bad; I used GO111MODULES (plural) instead of singular 🤦 - fixed

[theopenlab-ci]

Build succeeded.

• containerd-build-arm64 : NODE_FAILURE in 0s (non-voting)

[estesp]

nice work; I had looked at that commit too; not sure how I decided that wasn't the source of the issue! :) I did see that recent ginko no longer has that flag but probably got distracted with other work before trying to resolve what version we were using!

[estesp]

LGTM