From 82af52e8b7e62d36b6d16b757170b319ee5f213f Mon Sep 17 00:00:00 2001 From: Yingxin Cheng Date: Sat, 29 Jan 2022 10:39:13 +0800 Subject: [PATCH] test/crimson/test_messenger: increase timeout 120 seconds are still too short for make check, change to 300. Signed-off-by: Yingxin Cheng --- src/test/crimson/test_messenger.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/test/crimson/test_messenger.cc b/src/test/crimson/test_messenger.cc index bd549d4d6161..8c603d4615b7 100644 --- a/src/test/crimson/test_messenger.cc +++ b/src/test/crimson/test_messenger.cc @@ -3639,11 +3639,11 @@ int main(int argc, char** argv) ("v2-testpeer-islocal", bpo::value()->default_value(true), "create a local crimson testpeer, or connect to a remote testpeer"); return app.run(argc, argv, [&app] { - // This test normally succeeds within 60 seconds, so kill it after 120 + // This test normally succeeds within 60 seconds, so kill it after 300 // seconds in case it is blocked forever due to unaddressed bugs. - return seastar::with_timeout(seastar::lowres_clock::now() + 120s, do_test(app)) + return seastar::with_timeout(seastar::lowres_clock::now() + 300s, do_test(app)) .handle_exception_type([](seastar::timed_out_error&) { - logger().error("test_messenger timeout after 120s, abort! " + logger().error("test_messenger timeout after 300s, abort! " "Consider to extend the period if the test is still running."); // use the retcode of timeout(1) return 124; -- 2.47.3