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).
This commit is contained in:
Luke Parker 2023-09-26 17:28:41 -04:00
parent 2508633de9
commit 32a9a33226
No known key found for this signature in database

View file

@ -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