🧑‍🌾 `launch_testing_ros` freezing some builds without log output

[miguelgonrod]

Generated by Generative AI

No response

Operating System:

Ubuntu Noble

ROS version or commit hash:

Rolling

RMW implementation (if applicable):

No response

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 any of the jobs marked below
2. Run the job
3. Check the result (it isn't happening always)

Expected behavior

To build the job normally

Actual behavior

In some cases it is freezing in this section, and after 9 hours by policies the job is stopped

Additional information

Reference Builds

• https://ci.ros2.org/job/nightly_linux-rhel_debug/2567
• https://ci.ros2.org/job/nightly_linux-aarch64_debug/3441
• https://ci.ros2.org/job/nightly_win_rep/3966
• https://ci.ros2.org/job/nightly_linux-rhel_debug/2546
• https://ci.ros2.org/job/nightly_linux-rhel_release/2521/console
• https://ci.ros2.org/job/nightly_linux-rhel_debug/2543
• https://ci.ros2.org/job/nightly_linux-rhel_debug/2542
• https://ci.ros2.org/job/nightly_linux-aarch64_debug/3424
• https://ci.ros2.org/job/nightly_linux-aarch64_debug/3419
• https://ci.ros2.org/job/nightly_linux-rhel_debug/2538
• https://ci.ros2.org/job/nightly_linux-rhel_repeated/2514
• https://ci.ros2.org/job/nightly_linux-rhel_repeated/2513
• https://ci.ros2.org/job/nightly_linux-rhel_release/2514
• https://ci.ros2.org/job/nightly_linux-aarch64_debug/3416
• https://ci.ros2.org/job/nightly_linux-aarch64_release/3390

Log Output

10:29:32 [Processing: launch_testing_ros]
10:30:02 [Processing: launch_testing_ros]
10:30:32 [Processing: launch_testing_ros]

There is no output explaining the launch_testing_ros problem, maybe with verbose or adding additional logging to this package?
Beiing honest we don't know what is happenning

CC: @Crola1702

[Crola1702]

We just had a hung linux job on this package: https://ci.ros2.org/job/nightly_linux_debug/3715/

Here is the dump of ./ws/log:

launch_testing_ros_hung.tar.gz

[asymingt]

First failure in your list seemed to happen the day (Dec 16) after this merge (Dec 15):
ros2/launch_ros#511

[ros-discourse]

This issue has been mentioned on Open Robotics Discourse. There might be relevant details there:

https://discourse.openrobotics.org/t/ros-pmc-minutes-for-january-13th/52013/1

[ros-discourse]

This issue has been mentioned on Open Robotics Discourse. There might be relevant details there:

https://discourse.openrobotics.org/t/ros-pmc-minutes-for-january-20-2026/52015/1

[MiguelCompany]

First failure in your list seemed to happen the day (Dec 16) after this merge (Dec 15): ros2/launch_ros#511

ros2/ros2#1765 also happened that day, and ros2/rclcpp#3036 mentions the day after, so I think they may be related.
If that is the case, eProsima/Fast-DDS#6276 might fix this