FAIL: test_cli.TestROS2LifecycleCLI.test_set_lifecycle_node_invalid_transition[rmw_connextdds]
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/ws/install_isolated/launch_testing/lib/python3.14/site-packages/launch_testing/markers.py", line 61, in _wrapper
return func(self, *args, **kwargs)
File "/tmp/ws/src/ros2/ros2cli/ros2lifecycle/test/test_cli.py", line 325, in test_set_lifecycle_node_invalid_transition
assert not lifecycle_command.stdout
AssertionError: assert not '[RTI LICENSE] | RTI Connext licensed for prototype, research and non-commercial use only. USE FOR OTHER COMMERCIAL PU... User license@rti.com For non-production use only.\nPlease contact support@rti.com with any questions or comments.\n\n'
+ where '[RTI LICENSE] | RTI Connext licensed for prototype, research and non-commercial use only. USE FOR OTHER COMMERCIAL PU... User license@rti.com For non-production use only.\nPlease contact support@rti.com with any questions or comments.\n\n' = <launch_testing.tools.process.ProcessProxy object at 0x7b172a9a0a60>.stdout
The test fails because the RTI Connext license warning is unexpectedly written to stdout, causing the CLI test's empty-output assertion to fail.
Generated by Generative AI
No response
Operating System:
Ubuntu Resolute
ROS version or commit hash:
Rolling
RMW implementation (if applicable):
rmw_connextdds
RMW Configuration (if applicable):
No response
Client library (if applicable):
No response
'ros2 doctor --report' output
No response
Steps to reproduce issue
Expected behavior
Build without test regressions
Actual behavior
Tests failing because Connext RTI licence is catched in stdout
Additional information
Reference Build
Failing tests
Log Output
Flakyness 15 days
The test fails because the RTI Connext license warning is unexpectedly written to stdout, causing the CLI test's empty-output assertion to fail.