Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

test_cli.py misses launch_ros for rmw_cyclonedds_cpp

See original GitHub issue

This affects multiple packages, I’m still looking into which test_cli failures are just due to this. So far

ros2node: test_cli::test_list_node_count test_cli::test_list_all_nodes_count ros2service test_cli::test_list_count

With ros2node it gets the following for listing nodes. Inspecting the output of ros2 node list -a, it reports:

/_hidden_complex_node /_ros2cli_daemon_1 /complex_node

The test appears to be missing launch_ros

https://ci.ros2.org/view/nightly/job/nightly_win_extra_rmw_rel/673/testReport/ros2node.test/test_cli/test_cli/ https://ci.ros2.org/view/nightly/job/nightly_linux_extra_rmw_release/619/testReport/ros2node.test/test_cli/test_cli/

Issue Analytics

State:
Created 4 years ago
Comments:6

Top GitHub Comments

1reaction

brawnercommented, Mar 19, 2020

Now the behavior is more consistent among the different DDS implementations. Maybe the test just needs to be updated? It fails now with connext, fastrtps, cyclonedds

Some more examples https://ci.ros2.org/view/nightly/job/nightly_linux_release/1486/testReport/ros2service.src.ros2.ros2cli.ros2service.test/test_cli/test_cli/ https://ci.ros2.org/view/nightly/job/nightly_win_extra_rmw_rel/703/testReport/ros2node.src.ros2.ros2cli.ros2node.test/test_cli/test_cli/

0reactions

rotucommented, Mar 19, 2020

Ya. It looks like the nodes aren’t being “missed” - they just don’t exist anymore. And it seems to have been caused at least in part by that PR. So it’s a naughty test, not a misbehavior of ros2 node list -a -c.