Update timings for movel tests

The times are only rough and should reflect the trajectory time plus some overhead.
UniversalRobots · Jan 10, 2025 · b9c2235 · b9c2235
1 parent af71e80
commit b9c2235
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/tests/test_instruction_executor.cpp b/tests/test_instruction_executor.cpp
@@ -204,13 +204,13 @@ TEST_F(InstructionExecutorTest, execute_movel_success)
   ASSERT_TRUE(executor_->moveL({ -0.203, 0.263, 0.559, 0.68, -1.083, -2.076 }, 1.5, 1.5));
   auto end = std::chrono::steady_clock::now();
   auto duration = std::chrono::duration_cast<std::chrono::milliseconds>(end - start);
-  ASSERT_NEAR(duration.count(), 750, 100);
+  ASSERT_NEAR(duration.count(), 800, 150);
 
   start = std::chrono::steady_clock::now();
   ASSERT_TRUE(executor_->moveL({ -0.203, 0.463, 0.559, 0.68, -1.083, -2.076 }, 1.5, 1.5));
   end = std::chrono::steady_clock::now();
   duration = std::chrono::duration_cast<std::chrono::milliseconds>(end - start);
-  ASSERT_NEAR(duration.count(), 750, 100);
+  ASSERT_NEAR(duration.count(), 800, 150);
 
   // time parametrization
   start = std::chrono::steady_clock::now();
@@ -282,4 +282,4 @@ int main(int argc, char* argv[])
   }
 
   return RUN_ALL_TESTS();
-}
+}