From 370ec088e2bb141fdd3cccaaa9fbfdf51fc1968b Mon Sep 17 00:00:00 2001 From: Steve Macenski Date: Tue, 2 Apr 2024 15:10:39 -0700 Subject: [PATCH] Increasing test count from timeout handling changes (#4234) Signed-off-by: Steve Macenski Signed-off-by: enricosutera --- .../test/plugins/action/test_bt_action_node.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nav2_behavior_tree/test/plugins/action/test_bt_action_node.cpp b/nav2_behavior_tree/test/plugins/action/test_bt_action_node.cpp index 8aa1c3366e..d22ed27c7a 100644 --- a/nav2_behavior_tree/test/plugins/action/test_bt_action_node.cpp +++ b/nav2_behavior_tree/test/plugins/action/test_bt_action_node.cpp @@ -318,7 +318,7 @@ TEST_F(BTActionNodeTestFixture, test_server_timeout_success) // since the server timeout is 20ms and bt loop duration is 10ms, number of ticks should // be at most 2, but it can be 1 too, because the tickOnce may execute two ticks. - EXPECT_LE(ticks, 2); + EXPECT_LE(ticks, 3); EXPECT_GE(ticks, 1); } @@ -364,7 +364,7 @@ TEST_F(BTActionNodeTestFixture, test_server_timeout_failure) EXPECT_EQ(result, BT::NodeStatus::FAILURE); // since the server timeout is 90ms and bt loop duration is 10ms, number of ticks should be 9 - EXPECT_EQ(ticks, 9); + EXPECT_EQ(ticks, 10); // start a new execution cycle with the previous BT to ensure previous state doesn't leak into // the new cycle