ros2
🧑🌾 ros2cli daemon get publishers and subscribers by topic test failing in connextdds
Generated by Generative AI
No response
Operating System:
Ubuntu noble
ROS version or commit hash:
Rolling and Kilted
RMW implementation (if applicable):
rmw_connextdds
RMW Configuration (if applicable):
No response
Client library (if applicable):
No response
'ros2 doctor --report' output
No response
Steps to reproduce issue
- Run a build in Rolling or Kilted connextdds
- See test regression fail
Expected behavior
Tests should pass
Actual behavior
Tests are failing
Additional information
Reference builds:
Test regressions:
- ros2cli.ros2cli.test.test_ros2cli_daemon.test_get_publishers_info_by_topic
- ros2cli.ros2cli.test.test_ros2cli_daemon.test_get_subscriptions_info_by_topic
Comparing build repos diff points to #1040:
ros2/ros2cli:
type: git
url: https://github.com/ros2/ros2cli.git
- version: 9aec89715a62fca884f7e34d63456d2ee1b8a452
+ version: c0fabeaa7cdef097a92965104e3d809d9f6926f1
Log output:
test/test_ros2cli_daemon.py:232: in test_get_subscriptions_info_by_topic
assert test_subscription_info.qos_profile.history == \
E assert <HistoryPolicy.UNKNOWN: 3> == <HistoryPolicy.KEEP_LAST: 1>
E + where <HistoryPolicy.UNKNOWN: 3> = <rclpy.qos.QoSProfile object at 0x75cff096af10>.history
E + where <rclpy.qos.QoSProfile object at 0x75cff096af10> = <rclpy.topic_endpoint_info.TopicEndpointInfo object at 0x75cff0972500>.qos_profile
E + and <HistoryPolicy.KEEP_LAST: 1> = <rclpy.qos.QoSProfile object at 0x75cff13a3370>.history
The reason it wasn't caught on CI in the PR is that CI runs with sequential executor, while nightlies run with parallel executor.
@Crola1702 thanks for creating the issue for this problem.
i am not sure about the difference between sequential and parallel executor, but i can reproduce this issue with my local environment.
This issue has been mentioned on Open Robotics Discourse. There might be relevant details there:
https://discourse.ros.org/t/ros-pmc-minutes-for-july-1-2025/45001/1
This issue has been mentioned on Open Robotics Discourse. There might be relevant details there:
https://discourse.openrobotics.org/t/ros-pmc-minutes-for-november-11-2025/51100/1
@Crola1702 Checking builds apparently this fixed the issue. In rolling didn't happened in last build, in Kilted we have to check after rebuild.
