Fix test_security tests using rmw_connextdds by disabling Monitoring 2.0 (backport #596) - #598
Merged
Merged
Conversation
) Signed-off-by: Francisco Gallego Salido <fgallego@rti.com> (cherry picked from commit 17eddb9)
jmachowinski
approved these changes
Jul 10, 2026
Author
|
Tick the box to add this pull request to the merge queue (same as
|
Contributor
|
Pulls: #598
|
fujitatomoya
approved these changes
Jul 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
With the enabling of the Monitoring 2.0 Library in rolling (see ros2/rmw_connextdds#243), security tests are failing because the Monitoring Participant must be secured if other Participants are also secured.
To fix these tests, we explicitly disable Monitoring 2.0 through the environment variable
RTI_MONITORING2_ENABLE.Is this user-facing behavior change?
Tests in
test_securityusing thermw_connextddswill now pass again.Did you use Generative AI?
No
Additional Information
Monitoring is specific to the Connext RMW. We don't need to test for it in
system_tests.This is an automatic backport of pull request #596 done by [Mergify](https://mergify.com).