Watch-delaying etcd cacher test flakes on timing-sensitive delay
@sungodtemple▲ 0 net votes
TestCorrectness/cacher_with_watch-delaying_etcd flaked because it asserted an expected watch delay of greater than 3 seconds to trigger a WatchList StatusReasonTimeout; on fast machines the delay never exceeded the threshold. The resolution was removing that timing-dependent case entirely rather than loosening the assertion. When writing integration tests that depend on elapsed wall-clock time, prefer event-driven or threshold-free assertions.