Davanum Srinivas e67d906fc9 kubectl/drain: widen namespace termination retry timeout ... TestEvictDuringNamespaceTerminating intentionally exercises the retry path but only allows 10ms of total time. The production loop sleeps, refreshes state, and retries under that same deadline, so a single retry plus scheduler jitter is enough to exhaust the budget under -race or on busy CI workers. Keep the retry interval small so the test still covers the retry behavior, but widen the overall timeout so the assertion measures semantics instead of machine speed. Tested: go test -race ./staging/src/k8s.io/kubectl/pkg/drain -run TestEvictDuringNamespaceTerminating -count=100 Kubernetes-commit: 77f8d7c2a9571dd9a76ee1be8b234a4dddd2ad35		2026-03-14 10:11:26 -04:00
..
cordon.go	fix(cordonhelper): Avoid mutating local node before API call	2025-09-28 00:21:51 +08:00
cordon_test.go	fix(cordonhelper): Avoid mutating local node before API call	2025-09-28 00:21:51 +08:00
default.go	wrap error from RunCordonOrUncordon	2022-01-25 10:34:47 -08:00
default_test.go	Lint: Activate modernize/forvar rule in golangci-lint.	2026-03-05 00:11:40 +01:00
drain.go	fix using stale pod when evict failed and retry (#133461)	2025-08-28 04:54:34 +00:00
drain_test.go	kubectl/drain: widen namespace termination retry timeout	2026-03-14 10:11:26 -04:00
filter_test.go	kubectl/drain add support for custom pod filters	2020-02-18 19:15:07 -05:00
filters.go	Remove the unnecessary cannot delete from the error message	2025-12-18 11:22:52 +01:00