From 12c9acbf0cf4a12d632c7a73617161aa3e02f6bb Mon Sep 17 00:00:00 2001 From: Trevor Brown Date: Sun, 1 Nov 2026 00:17:54 -0400 Subject: [PATCH] events test: the stamp is within a minute of a second clock read, not ordered against it Review follow-up on #1766: a backward wall-clock step between the push and the test read made the ordering assertion flaky. Co-Authored-By: Claude Fable 5.1 --- crates/engine/src/events_tests.rs | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/crates/engine/src/events_tests.rs b/crates/engine/src/events_tests.rs index ad20974c5..304a8f8d1 100644 --- a/crates/engine/src/events_tests.rs +++ b/crates/engine/src/events_tests.rs @@ -53,7 +53,8 @@ fn events_are_stamped_with_the_wall_clock() { let r = log.poll(0, &comments(), 10, Duration::ZERO); let now = web_time::SystemTime::now().duration_since(web_time::UNIX_EPOCH).unwrap().as_secs_f64(); let time = r.events[0].time; - assert!(time > 1_700_000_000.0 && time <= now, "{time} is seconds since the Unix epoch, read just before {now}"); + // Within a minute of the same clock read afterwards (not ordered: the wall clock can step). + assert!(time > 1_700_000_000.0 && (time - now).abs() < 60.0, "{time} is seconds since the Unix epoch, read next to {now}"); } #[test]