From c522d63a97ce77c6d8ea12b384cad4909863e468 Mon Sep 17 00:00:00 2001
From: Mikhail Uvarov <arcusfelis@gmail.com>
Date: Wed, 31 Jan 2024 18:47:11 +0100
Subject: [PATCH] Do check manually in disco_node_down_timestamp_is_remembered
 testcase

---
 test/cets_SUITE.erl | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/test/cets_SUITE.erl b/test/cets_SUITE.erl
index 6db1c3f9..8a92f1af 100644
--- a/test/cets_SUITE.erl
+++ b/test/cets_SUITE.erl
@@ -2654,7 +2654,10 @@ disco_node_down_timestamp_is_remembered(Config) ->
 disco_logs_nodeup_after_downtime(Config) ->
     logger_debug_h:start(#{id => ?FUNCTION_NAME}),
     #{disco := Disco, node2 := Node2} = setup_two_nodes_and_discovery(Config, [wait, netsplit]),
-    %% At this point cets_disco should reconnect nodes back automatically.
+    %% At this point cets_disco should reconnect nodes back automatically
+    %% after retry_type_to_timeout(after_nodedown) time.
+    %% We want to speed this up for tests though.
+    Disco ! check,
     %% Receive a nodeup after the disconnect.
     %% This nodeup should contain the downtime_millisecond_duration field
     %% (initial nodeup should not contain this field).