mirror of
https://github.com/serai-dex/serai.git
synced 2025-01-10 12:54:35 +00:00
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:
parent
2508633de9
commit
32a9a33226
1 changed files with 4 additions and 1 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue