ros-controls / ros-controls/control_toolbox
Timeout of test_gravity_compensation
Open
Nobody has claimed this yet.
bug
CI
- Dominant language
- C++
- Stars
- 176
- Forks
- 124
- Avg merge
- 3h 44m
- Merged PRs (30d)
- 9
Description
build/control_toolbox/Testing/20250606-0454/Test.xml: 12 tests, 0 errors, 1 failure, 0 skipped
- test_gravity_compensation
<<< failure message
-- run_test.py: invoking following command in '/__w/control_toolbox/control_toolbox/ros_ws/build/control_toolbox':
- /__w/control_toolbox/control_toolbox/ros_ws/build/control_toolbox/test_gravity_compensation --ros-args --params-file /__w/control_toolbox/control_toolbox/ros_ws/src/1xaembwftwn/control_toolbox/control_toolbox/test/control_filters/test_gravity_compensation_parameters.yaml -- --gtest_output=xml:/__w/control_toolbox/control_toolbox/ros_ws/build/control_toolbox/test_results/control_toolbox/test_gravity_compensation.gtest.xml
[==========] Running 5 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 5 tests from GravityCompensationTest
[ RUN ] GravityCompensationTest.TestGravityCompensationFilterThrowsUnconfigured
>>>
build/control_toolbox/test_results/control_toolbox/test_gravity_compensation.gtest.xml: 1 test, 1 error, 0 failures, 0 skipped
- control_toolbox test_gravity_compensation.gtest.missing_result
<<< error message
The test did not generate a result file.
>>>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failing test executable test_gravity_compensation and its parameter file, test/control_filters/test_gravity_compensation_parameters.yaml. Read issue #384 for context, then reproduce the timeout and inspect why TestGravityCompensationFilterThrowsUnconfigured does not produce a result file; done means all five tests complete and the gtest XML is generated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100