From 9f9dcc7aa241f06469932befcc159cdb98dc12e6 Mon Sep 17 00:00:00 2001
From: flrnd <659650+flrnd@users.noreply.github.com>
Date: Mon, 28 Sep 2026 15:46:07 +0200
Subject: [PATCH] fix(tests): make EventCorrelatorTest timestamps deterministic

Avoid relying on Thread.sleep(100) to produce distinct timestamps.

The sleep was removed because the test only requires timestamp ordering,
not elapsed time. However, the Windows Bazel build showed that
OffsetDateTime.now() can return identical timestamps in consecutive calls
depending on the environment clock resolution.

Advance the timestamp explicitly instead, keeping the test deterministic
across different platforms.
---
 .../client/extended/event/EventCorrelatorTest.java           | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/extended/src/test/java/io/kubernetes/client/extended/event/EventCorrelatorTest.java b/extended/src/test/java/io/kubernetes/client/extended/event/EventCorrelatorTest.java
index 49309a9fa9..dbc9ffdc8d 100644
--- a/extended/src/test/java/io/kubernetes/client/extended/event/EventCorrelatorTest.java
+++ b/extended/src/test/java/io/kubernetes/client/extended/event/EventCorrelatorTest.java
@@ -144,8 +144,8 @@ void eventCorrelate(
       Boolean expectedSkip)
       throws Exception {
     EventCorrelator correlator = new EventCorrelator();
+    OffsetDateTime now = OffsetDateTime.now();
     for (CoreV1Event event : previousEvents) {
-      OffsetDateTime now = OffsetDateTime.now();
       event.setFirstTimestamp(now);
       event.setLastTimestamp(now);
       Optional<MutablePair<CoreV1Event, V1Patch>> result = correlator.correlate(event);
@@ -153,8 +153,7 @@ void eventCorrelate(
         correlator.updateState(event);
       }
     }
-    Thread.sleep(100);
-    OffsetDateTime now = OffsetDateTime.now();
+    now = now.plusNanos(10);
     newEvent.setFirstTimestamp(now);
     newEvent.setLastTimestamp(now);
     Optional<MutablePair<CoreV1Event, V1Patch>> result = correlator.correlate(newEvent);