-
Notifications
You must be signed in to change notification settings - Fork 42k
Closed
Labels
kind/flakeCategorizes issue or PR as related to a flaky test.Categorizes issue or PR as related to a flaky test.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.Indicates an issue or PR lacks a `sig/foo` label and requires one.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
Description
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:
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
Metadata
Metadata
Assignees
Labels
kind/flakeCategorizes issue or PR as related to a flaky test.Categorizes issue or PR as related to a flaky test.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.Indicates an issue or PR lacks a `sig/foo` label and requires one.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.