ros2 / ros2/ros2cli

🧑‍🌾 `ros2topic.ros2topic.test.test_bw_delay_hz.test_bw_delay_hz` failing in Kilted Zenoh

Open
#1,093 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted
Dominant language
Python
Stars
262
Forks
228
Avg merge
23h 15m
Merged PRs (30d)
12

Description

Generated by Generative AI

No response

Operating System:

Ubuntu Noble

ROS version or commit hash:

Kilted

RMW implementation (if applicable):

Zenoh

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 Kci Zenoh
  2. See test regression fail
Expected behavior

Test should not fail

Actual behavior

Test is failing

Additional information

Reference build:

Test regression:

Log output:

FAIL: test_bw_delay_hz.TestROS2TopicBwDelayHz.test_bw_basic (topic='/clitest/topic/bw_compatible_qos', provide_qos=True, compatible_qos=True)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/ws/src/ros2/ros2cli/ros2topic/test/test_bw_delay_hz.py", line 170, in helper_verb_basic
    assert re.search(success_regex, command.output, flags=re.MULTILINE), (
AssertionError: bw CLI did not print expected message
assert None
 +  where None = <function search at 0x79acf8335c60>('^[0-9]+ B/s from [0-9]+ messages$', 'WARNING: topic [/clitest/topic/bw_compatible_qos] does not appear to be published yet\n', flags=re.MULTILINE)
 +    where <function search at 0x79acf8335c60> = re.search
 +    and   'WARNING: topic [/clitest/topic/bw_compatible_qos] does not appear to be published yet\n' = <launch_testing.tools.process.ProcessProxy object at 0x79ace8107110>.output
 +    and   re.MULTILINE = re.MULTILINE

Last fail on Rolling was on 2025-07-08 (reference). Maybe we need to apply RMW Isolation? https://github.com/ros2/ros2cli/pull/1062

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.

Research direction

Start with ros2topic/test/test_bw_delay_hz.py, especially helper_verb_basic and the failing test output. Reproduce the Kilted Zenoh failure in the referenced Kci build and compare the expected bandwidth message with the warning shown in the log. Review the referenced RMW Isolation discussion; done means the test passes in the affected Zenoh build.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.