Skip to content

πŸ§‘β€πŸŒΎ ros2cli daemon get publishers and subscribers by topic test failing in connextddsΒ #1061

@Crola1702

Description

@Crola1702

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

  1. Run a build in Rolling or Kilted connextdds
  2. See test regression fail

Expected behavior

Tests should pass

Actual behavior

Tests are failing

Additional information

Reference builds:

Test regressions:

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.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions