Run relevant test_tracetools tests with all instrumented rmw impls

[christophebedard]

The test_tracetools tracing tests only currently run using the default rmw implementation. However, all "main" rmw implementations are instrumented, so we should run the tests that cover rmw instrumentation against all supported implementations.

Requires #104 for CI to pass.

[christophebedard]

Huh, I guess the non-default rmw implementations are not available for the Rpr job: https://build.ros2.org/job/Rpr__ros2_tracing__ubuntu_noble_amd64/51/cmake/new/

So if I want the Rpr to stay green, I can't do message(WARNING ...).

[christophebedard]

So if I want the Rpr to stay green, I can't do message(WARNING ...).

I switched to just message(...) and now the Rpr job is green.

@fujitatomoya can you take another look?

[clalancette]

I've left a couple of thoughts inline.

Besides that, do you have an idea of the impact on testing time? We are going from 5 tests to 15 here, so I just want to make sure this isn't adding a ton of time.

[christophebedard]

Besides that, do you have an idea of the impact on testing time? We are going from 5 tests to 15 here, so I just want to make sure this isn't adding a ton of time.

Local GitHub CI (which runs tests sequentially IIRC) only has Cyclone DDS and Fast DDS, so 2 out of 3. For the whole test_tracetools package:

1. Before: 42.6 seconds
2. After: 55.2 seconds

If I extrapolate to 2x the time difference (since this went from testing against 1 rmw implementation to 2 implementations), we'd get ~67.8 seconds with a third rmw implementation. Only 5 of the 13 tracing instrumentation tests get run against the list of 3 rmw implementations.

[christophebedard]

@ros-pull-request-builder retest this please

[christophebedard]

@ros-pull-request-builder retest this please

[clalancette]

Looks good to me with green CI.

[christophebedard]

• Linux
• Linux-aarch64
• Linux-rhel
• Windows