kubernetes: [Failing Test] bazel-test-master (periodic-kubernetes-bazel-test-master)

Which jobs are failing:

bazel-test-master (periodic-kubernetes-bazel-test-master)

Which test(s) are failing:

//cmd/kube-scheduler/app/go_default_test:run_1_of_3
//cmd/kube-scheduler/app/go_default_test:run_3_of_3
//pkg/util/iptables/go_default_test:run_2_of_3
//cmd/kube-scheduler/app/go_default_test:run_2_of_3
...

Since when has it been failing:

09-04-20 01:03 CDT

Testgrid link:

https://testgrid.k8s.io/sig-release-master-blocking#bazel-test-master

Reason for failure:

Errors differ between each of the failing tests. Looks like failure started between 26d0f8460 and fe8aa6eba.

Anything else we need to know:

/cc @kubernetes/ci-signal /priority critical-urgent /milestone v1.20

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 21 (20 by maintainers)

Most upvoted comments

Fixes identified:

Unresolved flakes (grouped by sig):

Query excluding unresolved/unmerged flakes (investigate anything flaking after 2020-09-05): https://testgrid.k8s.io/sig-release-master-blocking#bazel-test-master&width=20&sort-by-failures=&exclude-filter-by-regex=Overall|k8s.io/client-go/util/workqueue|k8s.io/client-go/tools/events|pkg/kubelet/volumemanager/reconciler|k8s.io/legacy-cloud-providers/vsphere|pkg/kubelet/config|pkg/controller/volume/attachdetach/reconciler|pkg/util/iptables|pkg/kubelet/cm/devicemanager|k8s.io/client-go/tools/portforward|k8s.io/apiserver/pkg/admission/plugin/webhook/validating|k8s.io/apiserver/pkg/storage/cacher|k8s.io/apiserver/pkg/admission/plugin/webhook/mutating

bazel job is removed in favor of the pull-kubernetes-unit job; I opened individual issues for the remaining flakes I saw referenced from here and added to the 1.21 milestone

/close

working on pkg/util/iptables

Almost certainly https://github.com/kubernetes/kubernetes/pull/93605, which means we have remaining unit test flakes