This command occasionally fails:
rostest dynamic_reconfigure test_cpp_client_single_threaded.test
example:
$ rostest dynamic_reconfigure test_cpp_client_single_threaded.test
<snip>
[ INFO] [1648122354.675674105] [/ref_server]: Reconfigure request: 0 0.000000 foo bar 0 0 Group1: 2 Group2: 3.333000 test string
[ INFO] [1648122354.678530562] [/ref_server]: Spinning node
[Testcase: testdynamic_reconfigure_single_threaded_client_test] ... ERROR!
ERROR: max time [1.0s] allotted for test [dynamic_reconfigure_single_threaded_client_test] of type [dynamic_reconfigure/dynamic_reconfigure-test_client_single_threaded]
File "/usr/lib/python3.8/unittest/case.py", line 60, in testPartExecutor
yield
File "/usr/lib/python3.8/unittest/case.py", line 676, in run
self._callTestMethod(testMethod)
File "/usr/lib/python3.8/unittest/case.py", line 633, in _callTestMethod
method()
File "/opt/ros/noetic/lib/python3/dist-packages/rostest/runner.py", line 148, in fn
self.test_parent.run_test(test)
File "/opt/ros/noetic/lib/python3/dist-packages/rostest/rostest_parent.py", line 132, in run_test
return self.runner.run_test(test)
File "/opt/ros/noetic/lib/python3/dist-packages/roslaunch/launch.py", line 701, in run_test
raise RLTestTimeoutException(
--------------------------------------------------------------------------------
[ROSTEST]-----------------------------------------------------------------------
SUMMARY
* RESULT: FAIL
* TESTS: 0
* ERRORS: 1
* FAILURES: 0
If I change the timeout in the launch file from:
time-limit="1.0"
to
time-limit="2.0"
This command occasionally fails: rostest dynamic_reconfigure test_cpp_client_single_threaded.test
example:
If I change the timeout in the launch file from:
time-limit="1.0"totime-limit="2.0"it consistently succeeds. Tested on noetic.