Skip to content
This repository has been archived by the owner on Feb 4, 2021. It is now read-only.

New test failures in test_launch_ros test_track_node_names #272

Closed
nuclearsandwich opened this issue Apr 16, 2020 · 2 comments
Closed

New test failures in test_launch_ros test_track_node_names #272

nuclearsandwich opened this issue Apr 16, 2020 · 2 comments
Assignees
@mjcarroll

Comments

@nuclearsandwich
Copy link
Member

The following tests are failing across all platforms as of last night's nightlies.

test_launch_ros.src.ros2.launch_ros.test_launch_ros.test.test_launch_ros.test_track_node_names.test_launch_composable_node_with_names
test_launch_ros.src.ros2.launch_ros.test_launch_ros.test.test_launch_ros.test_track_node_names.test_launch_composable_node_without_component_name
test_launch_ros.src.ros2.launch_ros.test_launch_ros.test.test_launch_ros.test_track_node_names.test_launch_nodes_with_same_names
test_launch_ros.src.ros2.launch_ros.test_launch_ros.test.test_launch_ros.test_track_node_names.test_launch_nodes_with_different_names
@nuclearsandwich nuclearsandwich mentioned this issue Apr 16, 2020
Merged
@mjcarroll mjcarroll self-assigned this Apr 16, 2020
@mjcarroll mjcarroll mentioned this issue Apr 16, 2020
Merged
@mjcarroll
Copy link
Member

Corresponding PR fixes those tests and has been merged.

@nuclearsandwich
Copy link
Member Author

It's not policy but I tend to wait to close build_farmer issues until the next round of nightlies comes back fixed. Not expecting to need to reopen this in the morning though.

@nuclearsandwich nuclearsandwich mentioned this issue Apr 17, 2020
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mjcarroll mjcarroll

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mjcarroll @nuclearsandwich