CI Signal Report for Week 2 of 1.24, 2022-01-19 🟢

[Leonard Pahlke]

CI Signal Report for Week 2 of 1.24, 2022-01-19

Hello and welcome to the CI Signal report for the Kubernetes 1.24 release cycle. This is week 3 of the release cycle!

The CI Signal team observes closely

• master-blocking

Overall our status is Green. Master blocking looks good. The failing job gce-device-pluging-gpu-master has been reported and seems to be a duplicate test which now has been removed.

This week we investigated:

• A flaky test on master-blocking#gci-gce-ingress. The issue has been picked up. GitHub issue #107530,  slack thread

For more information and the latest state visit the CI Signal Project board.

Questions or feedback? Reach us on Slack at #sig-release or #release-ci-signal. Thank you!

[徐XuPaco俊杰Junjie]

The failing job gce-device-pluging-gpu-master has been reported and seems to be a duplicate test which now has been removed.

- The reason is that dockershim has been removed since 1.24. 

```

I0119 09:34:26.862649    2042 flags.go:64] FLAG: --container-runtime-endpoint="unix:///var/run/dockershim.sock"

```

Got the log from the master node of the testing https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-device-plugin-gpu/1483733607188008960/artifacts/bootstrap-e2e-master/.

'Leonard Pahlke' via dev <d...@kubernetes.io> 于2022年1月19日周三 18:23写道：

--
You received this message because you are subscribed to the Google Groups "dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/504be630-478b-41eb-9f4a-3ec1cccff898n%40kubernetes.io.

--

一切皆有可能！