/test all

/test pull-containerd-build
/test pull-containerd-node-e2e

@dims not sure how to figure out the e2e failure as it appears containerd isn't running (the socket file does not exist), but I don't see any errors explaining why it isn't..

@estesp from this log

Feb 19 18:10:40 tmp-node-e2e-d927e36f-ubuntu-gke-1804-1-16-v20200330 configure.sh[1805]: ++ echo master:e58be59cbded3dcadaf67164fdc37eb52afed66c,5056:e541b9b6d2f3649959bc050ab90566c4c9139278
Feb 19 18:10:40 tmp-node-e2e-d927e36f-ubuntu-gke-1804-1-16-v20200330 configure.sh[1805]: + deploy_dir=9773450dd82256b5520199d7cca8396adb2e727d
Feb 19 18:10:40 tmp-node-e2e-d927e36f-ubuntu-gke-1804-1-16-v20200330 configure.sh[1805]: + deploy_path=cri-containerd-staging/9773450dd82256b5520199d7cca8396adb2e727d
Feb 19 18:10:40 tmp-node-e2e-d927e36f-ubuntu-gke-1804-1-16-v20200330 configure.sh[1805]: ++ curl -f --ipv4 --retry 6 --retry-delay 3 --silent --show-error https://storage.googleapis.com/cri-containerd-staging/9773450dd82256b5520199d7cca8396adb2e727d/latest
Feb 19 18:10:40 tmp-node-e2e-d927e36f-ubuntu-gke-1804-1-16-v20200330 configure.sh[1805]: curl: (22) The requested URL returned error: 404
Feb 19 18:10:40 tmp-node-e2e-d927e36f-ubuntu-gke-1804-1-16-v20200330 configure.sh[1805]: + version=

/test pull-containerd-node-e2e

/test pull-containerd-node-e2e

/test pull-containerd-build

/test pull-containerd-node-e2e

@dims any ideas? originally the problem was that the wrong bucket was being looked in because I added a commit between the "working" pull-containerd-build and the failing ..node-e2e runs; after fixing that I'm now getting:

Start Test Suite on Host tmp-node-e2e-483a515e-cos-81-12871-1245-10
timeout: failed to run command './ginkgo': Permission denied

Seems now that we aren't running CRI tests regularly post-merge maybe things are getting stale--we probably need to find some actions magic to trigger node-e2e tests on any commits that change CRI code or just run it daily via actions cron?

/test pull-containerd-node-e2e

going to try one last time to see if the gingko permission problem still persists. i don't think it will work as the underlying issue i saw in #5056 (comment) is still there. will dig into this more today

failed : curl -f --ipv4 --retry 6 --retry-delay 3 --silent --show-error https://storage.googleapis.com/cri-containerd-staging/6f7489c0425b8b1f95d833592598f037fc138745/latest is failing
succeeded : curl -f --ipv4 --retry 6 --retry-delay 3 --silent --show-error https://storage.googleapis.com/cri-containerd-staging/containerd/6f7489c0425b8b1f95d833592598f037fc138745/latest

Looks like we introduced a containerd directory and forgot to update the script?

screen shot from https://storage.googleapis.com/cri-containerd-staging/ :

Build succeeded.

• containerd-build-arm64 : SUCCESS in 5m 48s (non-voting)

Looks like go1.16.1 comes out tomorrow. Probably makes sense to wait and update to that?

@kevpar agreed; it's out but actions env hasn't updated their config file yet.. usually within 24 hours. As soon as it's available I'll update the PR

Build succeeded.

• containerd-build-arm64 : SUCCESS in 6m 07s (non-voting)

whoot ... time to move up local development environment to go 1.16.1!

Removed the cherry pick since we now have #5178 after the quick turnaround of another Go point release.