Skip to content

Conversation

@emersonknapp
Copy link
Contributor

Followup to ros2/rmw#301 - adding a compliance test so that RMW implementations are guaranteed to handle these values properly.

Tests pass locally against all default checked-out RMW implementations:

  • rmw_fastrtps
  • rmw_cyclonedds
  • rmw_connext
  • rmw_connextdds

For context, ros2/rosbag2#756 was an uncaught case of this being a problem. It led to ros2/rmw_connextdds#43, where @jacobperron recommended I create this test.

For a failing case, I reverted ros2/rmw_connextdds#43 in a branch, and rant this test against that version to see a failure.

Copy link
Contributor

@clalancette clalancette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to me with green CI. Though it might be good to have @jacobperron review before merging.

@emersonknapp
Copy link
Contributor Author

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

Copy link
Member

@jacobperron jacobperron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jacobperron jacobperron merged commit c502d16 into ros2:master Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants