ros2 / ros2/launch

[launch_testing]: Nightly test failure with rmw_zenoh

Open
#904 0 comments 0 reactions 1 assignee View on GitHub

@Yadunund is already working on this.

Since Aug 14, 2025.

bug
Dominant language
Python
Stars
155
Forks
182
Avg merge
2d 14h
Merged PRs (30d)
6

Description

Generated by Generative AI

No response

Operating System:

Ubuntu 24.04

ROS version or commit hash:

latest rolling

RMW implementation (if applicable):

No response

RMW Configuration (if applicable):

No response

Client library (if applicable):

No response

'ros2 doctor --report' output
ros2 doctor --report
<COPY OUTPUT HERE>
Steps to reproduce issue

https://build.ros2.org/job/Rci__nightly-zenoh_ubuntu_noble_amd64/143/testReport/launch_testing_ros.test.examples/wait_for_topic_launch_test/wait_for_topic_launch_test/](https://build.ros2.org/job/Rci__nightly-zenoh_ubuntu_noble_amd64/143/testReport/launch_testing_ros.test.examples/wait_for_topic_launch_test/wait_for_topic_launch_test/)

Expected behavior

Test passes

Actual behavior
===============================================================================================================================================================================================================
FAIL: wait_for_topic_launch_test.TestFixture.test_topics_unsuccessful
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/ws/src/ros2/launch_ros/launch_testing_ros/test/examples/wait_for_topic_launch_test.py", line 104, in test_topics_unsuccessful
    assert wait_for_node_object.topics_received() == expected_topics
AssertionError: assert {'chatter_0',..., 'chatter_4'} == {'chatter_0',..., 'chatter_4'}
  Extra items in the right set:
  'chatter_3'
  'chatter_2'
  Use -v to get more diff


===============================================================================================================================================================================================================
FAIL: wait_for_topic_launch_test.TestFixture.test_trigger_function
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/ws/src/ros2/launch_ros/launch_testing_ros/test/examples/wait_for_topic_launch_test.py", line 122, in test_trigger_function
    assert wait_for_node_object.wait(is_trigger_called)
AssertionError: assert False
 +  where False = <bound method WaitForTopics.wait of <launch_testing_ros.wait_for_topics.WaitForTopics object at 0x7954b40c7200>>([True])
 +    where <bound method WaitForTopics.wait of <launch_testing_ros.wait_for_topics.WaitForTopics object at 0x7954b40c7200>> = <launch_testing_ros.wait_for_topics.WaitForTopics object at 0x7954b40c7200>.wait

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.