rmw_connextdds icon indicating copy to clipboard operation
rmw_connextdds copied to clipboard

:farmer: Jazzy and humble ConnextDDS builds tests failing due to timeout waiting for process to finish

Open miguelgonrod opened this issue 1 month ago • 3 comments

System Info

  • OS
    • Ubuntu 24.04 and Ubuntu 22.04
  • ROS version and installation type
    • Jazzy and humble
  • RTI Connext DDS version and installation type
    • Rolling

Bug Description

performance tests from projectroot and buildfarm_perf_test are failing and sending a SIGINT

Expected Behavior

The tests to pass without errors

How to Reproduce

  1. go to https://build.ros2.org/job/Jci__nightly-performance_ubuntu_noble_amd64/ or https://build.ros2.org/job/Hci__nightly-performance_ubuntu_jammy_amd64 builds
  2. build the job
  3. See test failing

Additional context

Reference Builds

Tests Failing

  • projectroot.test.test_performance_rmw_connextdds_async_Array8m
  • projectroot.test.test_performance_rmw_connextdds_async_PointCloud8m
  • projectroot.test.test_performance_rmw_connextdds_sync_Array8m
  • buildfarm_perf_tests.PerformanceTestResults.test_results_rmw_connextdds
  • buildfarm_perf_tests.PerformanceTestResults.test_results_rmw_connextdds
  • buildfarm_perf_tests.PerformanceTestResults.test_results_rmw_connextdds

Flaky ratio of projectroot.test.test_performance_rmw_connextdds_async_Array8m last 15 days

job_name last_fail first_fail build_count failure_count failure_percentage
Jci__nightly-performance_ubuntu_noble_amd64 2025-11-20 2025-11-14 6 3 50.0
Hci__nightly-performance_ubuntu_jammy_amd64 2025-11-18 2025-11-14 4 3 75.0

Log output

[INFO] [launch]: Default logging verbosity is set to INFO
test_results_rmw_connextdds (buildfarm_perf_tests.PerformanceTestResults.test_results_rmw_connextdds) ... [INFO] [perf_test-1]: process started with pid [1498]
FAIL

======================================================================
FAIL: test_results_rmw_connextdds (buildfarm_perf_tests.PerformanceTestResults.test_results_rmw_connextdds)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/ws2/build_isolated/buildfarm_perf_tests/test/test/test_performance_rmw_connextdds_async_PointCloud8m.py", line 243, in test_results_rmw_connextdds
    assert_wait_for_successful_exit(proc_info, process, timeout)
  File "/tmp/ws2/install_isolated/buildfarm_perf_tests/lib/python3.12/site-packages/buildfarm_perf_tests/launch.py", line 27, in assert_wait_for_successful_exit
    proc_info.assertWaitForShutdown(process, timeout=timeout)
  File "/tmp/ws/install_isolated/launch_testing/lib/python3.12/site-packages/launch_testing/proc_info_handler.py", line 141, in assertWaitForShutdown
    assert success, "Timed out waiting for process '{}' to finish".format(process)
           ^^^^^^^
AssertionError: Timed out waiting for process '<launch_ros.actions.node.Node object at 0x7d2535afcc20>' to finish

----------------------------------------------------------------------
Ran 1 test in 60.002s

FAILED (failures=1)
[INFO] [perf_test-1]: sending signal 'SIGINT' to process[perf_test-1]
[perf_test-1] [INFO] [1763670260.838108631] [rclcpp]: signal_handler(signum=2)
[INFO] [perf_test-1]: process has finished cleanly [pid 1498]

----------------------------------------------------------------------

CC: @crola1702

miguelgonrod avatar Nov 21 '25 14:11 miguelgonrod