You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we look to run CI with rmw_zenoh, a non-DDS based middleware which would not support any cross-vendor tests, we'll need a way to skip running multi-RMW tests part of test_communication. At present system_tests/test_communication sets SKIP_MULTI_RMW_TESTS to OFF by default while explictly excluding certain cross-vendor tests for certain DDS middleware combinations.
If we add rmw_zenoh to the ros2.repos file and run CI, we can expect failures across all cros-vendor tests.
One "easy" way to resolve this is to add further exceptions to the CMakeLists.txt linked above for rmw_zenoh.
Another suggestion from @cottsay is to be able to infer "groups" of RMWs that are expected to be compatible on a per-test basis.
The text was updated successfully, but these errors were encountered:
Yadunund
changed the title
Skipping multi-RMW tests for rmw_zenoh defined in test_communication
Skipping multi-RMW tests defined in test_communication for rmw_zenoh
Feb 24, 2025
As we look to run CI with
rmw_zenoh
, a non-DDS based middleware which would not support any cross-vendor tests, we'll need a way to skip running multi-RMW tests part oftest_communication
. At presentsystem_tests/test_communication
sets SKIP_MULTI_RMW_TESTS to OFF by default while explictly excluding certain cross-vendor tests for certain DDS middleware combinations.If we add
rmw_zenoh
to theros2.repos
file and run CI, we can expect failures across all cros-vendor tests.One "easy" way to resolve this is to add further exceptions to the
CMakeLists.txt
linked above forrmw_zenoh
.Another suggestion from @cottsay is to be able to infer "groups" of RMWs that are expected to be compatible on a per-test basis.
Related to #429.
The text was updated successfully, but these errors were encountered: