mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-05-22 18:08:54 -04:00
1f59ea104a
Drops f.WithFlaky() from two test blocks where the tag has become stale: - [sig-node] kubelet host cleanup with volume mounts [HostCleanup] (covers both NFS sub-tests: active and sleeping client pods) - [sig-storage] PersistentVolumes-local "should set different fsGroup for second pod if first pod is deleted" (covers all 8 volume-type variants from the parameterized parent) Testgrid evidence -- both dashboards show consistent passes across all 30 recent runs: https://testgrid.k8s.io/google-gce#gci-gce-flaky&include-filter-by-regex=Flaky https://testgrid.k8s.io/sig-testing-misc#gce-cos-master-flaky-repro&include-filter-by-regex=Flaky History: - HostCleanup was tagged [Flaky] in PR 41659 (merged 2017-04-13) as a quick workaround for parallel-execution interference with disruptive tests; the follow-up "remove [Flaky]" PR mentioned in that body never landed. Root-cause issue 31272 ("Hung volumes can wedge the kubelet") remains open. - fsGroup test was tagged [Flaky] in PR 75015 (merged 2019-03-06) to skip a race in DesiredStateOfWorld re-adding terminating-pod volumes. Root-cause issue 73168 ("Do not remount volume again after it is detached") remains open. The obsolete TODO comment referencing that issue is also removed. If either test regresses, the safe rollback is to restore f.WithFlaky() and reopen the conversation on issue 31272 / 73168. |
||
|---|---|---|
| .. | ||
| apparmor.go | ||
| container_termination_metrics.go | ||
| crictl.go | ||
| events.go | ||
| examples.go | ||
| framework.go | ||
| gpu.go | ||
| kubelet.go | ||
| kubelet_authz.go | ||
| kubelet_perf.go | ||
| mount_propagation.go | ||
| node_lifecycle.go | ||
| node_problem_detector.go | ||
| OWNERS | ||
| pod_admission.go | ||
| pod_gc.go | ||
| pod_resize.go | ||
| pods.go | ||
| pre_stop.go | ||
| README.md | ||
| runtimeclass.go | ||
| security_context.go | ||
| ssh.go | ||
| taints.go | ||
WARNING: Do not add tests in this directory
There are two types of end-to-end tests in Kubernetes:
Tests located in ${KUBE_ROOT}/test/e2e/common are shared by both Cluster
and Node E2E test jobs. Tests in ${KUBE_ROOT}/test/e2e_node are exclusively
owned by Node E2E. If you want to add a test, most likely than not, you want
to add the test to one of the two directories mentioned above. If you are
unsure, please check with the OWNER of the directory. This directory currently
contains misplaced and legacy tests; they will be cleaned up in the future.