Could you add a test case in https://github.com/ros2/rmw_implementation/tree/master/test_rmw_implementation?

I don't need a test that actually confirms that all messages were acked (which is a bit hard to test), only test basic things:
e.g. passing a nullptr publisher returns an error, passing a valid BEST_EFFORT publisher always return immediatly RMW_RET_OK, etc.

Could you add a test case in https://github.com/ros2/rmw_implementation/tree/master/test_rmw_implementation?

I don't need a test that actually confirms that all messages were acked (which is a bit hard to test), only test basic things:
e.g. passing a nullptr publisher returns an error, passing a valid BEST_EFFORT publisher always return immediatly RMW_RET_OK, etc.

Okay. I add a simple test case (commit: cc154d9).
FYI, I add more test cases (such as timeout) in rcl PR ros2/rcl#913).

@ros-pull-request-builder retest this please (this should pass now)

@Barry-Xu-2018 can you check the test failures?

@ivanpauno

The failure is related to test_rmw_implementation.TestPublisherUse__rmw_cyclonedds_cpp.wait_for_all_acked_with_best_effort .
It is because ros2/rmw_cyclonedds#294 isn't merged now.

Could you check and merge it ?

Thanks @Barry-Xu-2018, I was sure I merged that one 😄

@ivanpauno

After ros2/rmw_cyclonedds#294 is merged, we should re-execute CI.
Could you help to execute CI again ?

@ros-pull-request-builder retest this please

CC: @Barry-Xu-2018 @ivanpauno

The PR checker should pass after ros/rosdistro#29924 is merged.
No need to run CI again, this is only wrapping new API and adding tests for it.

Thanks for the patience, but merging changes in rmw_* without breaking the rolling builds is a long process ...

@ros-pull-request-builder retest this please

finally ... 😃
going in!!