:farmer: benchmark_executor tests consistently timeout on Ubuntu Resolute AMD64

Generated by Generative AI

No response

Operating System:

Ubuntu Resolute

ROS version or commit hash:

Rolling and Lyrical

RMW implementation (if applicable):

No response

RMW Configuration (if applicable):

No response

Client library (if applicable):

No response

'ros2 doctor --report' output

Steps to reproduce issue

1. Go to https://build.ros2.org/job/Rci__benchmark_ubuntu_resolute_amd64
2. Build a job
3. See tests failing almost consistently

Expected behavior

Build without errors

Actual behavior

Timing out in two benchmark tests

Additional information

Reference Build

• Rci__benchmark_ubuntu_resolute_amd64#81

Failing tests

• projectroot.test.benchmark.benchmark_executor
• projectroot.test.benchmark.benchmark_init_shutdown

Log Output

9: 2026-09-13T05:45:03-08:00
9: Running /tmp/ws2/build_isolated/rclcpp/test/benchmark/benchmark_executor
9: Run on (4 X 3400.88 MHz CPU s)
9: CPU Caches:
9:   L1 Data 32 KiB (x2)
9:   L1 Instruction 32 KiB (x2)
9:   L2 Unified 1024 KiB (x2)
9:   L3 Unified 25344 KiB (x1)
9: Load Average: 1.97, 1.80, 1.43
9: -----------------------------------------------------------------------------------------------------------------------------------------------
9: Benchmark                                                                                     Time             CPU   Iterations UserCounters...
9: -----------------------------------------------------------------------------------------------------------------------------------------------
9: PerformanceTestExecutor/single_thread_executor_spin_some                                  31144 ns        31207 ns        24274 heap_allocations=40.0036
9: PerformanceTestExecutor/multi_thread_executor_spin_some                                   29316 ns        29382 ns        24710 heap_allocations=40.0035
9: PerformanceTestExecutor/cbg_executor_spin_some                                            24912 ns        24935 ns        28181 heap_allocations=61.2505
9: PerformanceTestExecutor/single_thread_executor_wait_for_work                               7884 ns         7788 ns        95836 heap_allocations=4.00091
9: PerformanceTestExecutor/multi_thread_executor_wait_for_work                                8522 ns         8344 ns        85781 heap_allocations=4.00101
9: PerformanceTestExecutor/single_thread_executor_wait_for_work_rebuild                      14856 ns        14190 ns        47299 heap_allocations=326.549
9: PerformanceTestExecutor/multi_thread_executor_wait_for_work_rebuild                       15348 ns        14619 ns        47806 heap_allocations=326.605
9: CascadedPerformanceTestExecutor/single_thread_executor_spin                               51905 ns         6545 ns       106078 heap_allocations=18.8541u
2/7 Test  #9: benchmark_executor ....................***Timeout  60.01 sec

Flakyness 15 days

job_name	last_fail	first_fail	build_count	failure_count	failure_percentage
Rci__benchmark_ubuntu_resolute_amd64	2026-09-13	2026-09-01	10	9	90.0
Lci__benchmark_ubuntu_resolute_amd64	2026-09-10	2026-09-02	4	3	75.0

Happening since build #1

Reproduce the failures from the Rci__benchmark_ubuntu_resolute_amd64 job, starting with the benchmark_executor and benchmark_init_shutdown tests. Compare their behavior with the reference build and the reported 60-second timeout on Ubuntu Resolute AMD64. Done means both benchmark tests complete reliably without timing out on the affected jobs.