-
Notifications
You must be signed in to change notification settings - Fork 190
Use rmw_test_fixture to isolate ros2cli tests #1062
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Scott K Logan <[email protected]>
|
PR job failures look real, reverting to draft until they're solved. EDIT: Of course, we'll need a release of |
Signed-off-by: Scott K Logan <[email protected]>
31ecfaa to
9c6c5c9
Compare
|
@ros-pull-request-builder retest this EDIT: Manual retry shows only the same two test failures we've had in this package for a while now: https://build.ros2.org/job/Rpr__ros2cli__ubuntu_noble_amd64/218/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm with green CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Excited to see this land!
|
Rerunning CI since it's been a while CI_BRANCH_TO_TEST: cottsay/rmw-test-isolation |
|
@Mergifyio backport kilted |
✅ Backports have been created
|
Signed-off-by: Scott K Logan <[email protected]> (cherry picked from commit 75e004a)
Description
Use the
rmw_test_isolationsystem for creating a communication sandbox for each test.Fixes # (issue)
Is this user-facing behavior change?
Yes,
ros2cli.helpers.get_rmw_additional_envwill no longer enable multicast for Zenoh.Did you use Generative AI?
No