From 32a9a33226757c8c3a7c4ac3ed8a50ab57196450 Mon Sep 17 00:00:00 2001 From: Luke Parker Date: Tue, 26 Sep 2023 17:28:41 -0400 Subject: [PATCH] Adjust sync test timeout to resolve infreuqent failure This isn't an unacceptable timeout. It matches a prior timeout. I'm unsure why it's now needed to be extended though. My best guess is the test runtime is single threaded and there's now new overhead in the task management (or perhaps higher latency now that messages per-tributary is serialized). --- coordinator/src/tests/tributary/sync.rs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/coordinator/src/tests/tributary/sync.rs b/coordinator/src/tests/tributary/sync.rs index af4bb0c7..3dfc3757 100644 --- a/coordinator/src/tests/tributary/sync.rs +++ b/coordinator/src/tests/tributary/sync.rs @@ -85,8 +85,11 @@ async fn sync_test() { // It shouldn't automatically catch up. If it somehow was, our test would be broken // Sanity check this let tip = tributaries[0].tip().await; - sleep(Duration::from_secs(2 * block_time)).await; + // Wait until a new block occurs + sleep(Duration::from_secs(3 * block_time)).await; + // Make sure a new block actually occurred assert!(tributaries[0].tip().await != tip); + // Make sure the new block alone didn't trigger catching up assert_eq!(syncer_tributary.tip().await, spec.genesis()); // Start the heartbeat protocol