:farmer: Rci__nightly-zenoh_ubuntu_noble build failing by timeout just in zenoh

[miguelgonrod]

Generated by Generative AI

No response

Operating System:

Ubuntu Noble

ROS version or commit hash:

Rolling

RMW implementation (if applicable):

rmw_zenoh

RMW Configuration (if applicable):

No response

Client library (if applicable):

No response

'ros2 doctor --report' output

No response

Steps to reproduce issue

1. Go to https://build.ros2.org/job/Rci__nightly-zenoh_ubuntu_noble_amd64
2. Build the job
3. See the build failing

Expected behavior

To build successfully

Actual behavior

Building by timeouts

Additional information

Reference Build

• https://build.ros2.org/job/Rci__nightly-zenoh_ubuntu_noble_amd64/359 (Last build)
• since https://build.ros2.org/job/Rci__nightly-zenoh_ubuntu_noble_amd64/335/

Log output

04:14:48.472 test/examples/set_param_launch_test.py RRF                               [ 70%]
04:23:20.500 test/examples/talker_listener_launch_test.py RRF                         [ 80%]
06:30:00.028 Build timed out (after 390 minutes). Marking the build as failed.
06:30:00.046 Build was aborted

Looking at the timestamps, this jobs is getting stuck in test/examples/talker_listener_launch_test.py. We didn't reported this in launch testing ros because this is only happenning in zenoh.

First approach we had was to increase the time limit from 300 minutes to 390 minutes because working jobs had times near the limit, but that wasn't the problem.

CC: @Crola1702