Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_cli.py misses launch_ros for rmw_cyclonedds_cpp #456

Closed
brawner opened this issue Feb 25, 2020 · 7 comments
Closed

test_cli.py misses launch_ros for rmw_cyclonedds_cpp #456

brawner opened this issue Feb 25, 2020 · 7 comments
Assignees

Comments

@brawner
Copy link

brawner commented Feb 25, 2020

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/

@brawner brawner changed the title ros2node for rmw_cyclonedds_cpp: test_cli::test_list_node_count/test_list_all_nodes_count misses launch_ros test_cli.py misses launch_ros for rmw_cyclonedds_cpp Feb 25, 2020
@rotu
Copy link

rotu commented Mar 19, 2020

@brawner please clarify what you mean that it "misses" launch_ros. What is the issue?

@brawner
Copy link
Author

brawner commented Mar 19, 2020

During the above linked failures, the expected number of nodes doesn't match what it actually finds. When I was digging into this, the launch_ros node is running, but it's not found during this test

Traceback (most recent call last):
  File "/home/jenkins-agent/workspace/nightly_linux_extra_rmw_release/ws/install/launch_testing/lib/python3.6/site-packages/launch_testing/markers.py", line 48, in _wrapper
    return func(self, *args, **kwargs)
  File "/home/jenkins-agent/workspace/nightly_linux_extra_rmw_release/ws/src/ros2/ros2cli/ros2node/test/test_cli.py", line 153, in test_list_all_nodes_count
    assert int(output_lines[0]) == 4
AssertionError: assert 3 == 4
 +  where 3 = int('3')

It still is happening in recent tests, you can search the consoleText:
FAIL: test_list_all_nodes_count[rmw_cyclonedds_cpp] (test_cli.TestROS2NodeCLI)
https://ci.ros2.org/view/nightly/job/nightly_linux_extra_rmw_release/653/consoleText

@rotu
Copy link

rotu commented Mar 19, 2020

Ah... Seems to be caused by ros2/launch_ros#128, which by eliminating default_launch_description.py got rid of extra implementation nodes.

@brawner
Copy link
Author

brawner commented Mar 19, 2020

This failure has been ongoing for awhile now and still occurs after that PR was merged, but I'm also not familiar enough with this everything involved to suggest what's causing the issue.

@rotu
Copy link

rotu commented 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.

@brawner
Copy link
Author

brawner commented 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/

@clalancette
Copy link
Contributor

This is an old issue, and I don't think that we are having this exact problem anymore in CI, so I'm going to close this. Feel free to reopen if you still think this is a problem.

@clalancette clalancette closed this as not planned Won't fix, can't repro, duplicate, stale Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants