:farmer: test_cli failure caused by unexpected Connext license warning in stdout

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

1. Go to any of the jobs listed below
2. Build a job
3. See tests failing

Expected behavior

Build without test regressions

Actual behavior

Tests failing because Connext RTI licence is catched in stdout

Additional information

Reference Build

• Rci__nightly-connext_ubuntu_resolute_amd64#143
• https://ci.ros2.org/job/nightly_linux-aarch64_repeated/3697
• https://build.ros2.org/job/Rci__nightly-debug_ubuntu_resolute_amd64/142
• https://build.ros2.org/job/Rci__nightly-release_ubuntu_resolute_amd64/235
• https://ci.ros2.org/job/nightly_linux-aarch64_debug/3698
• https://ci.ros2.org/job/nightly_linux-aarch64_release/3688

Failing tests

• ros2lifecycle.ros2lifecycle.test.test_cli.test_cli

Log Output

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

Flakyness 15 days

job_name	last_fail	first_fail	build_count	failure_count	failure_percentage
nightly_linux-aarch64_repeated	2026-09-17	2026-09-02	14	14	100.0
nightly_linux-aarch64_release	2026-09-17	2026-09-03	14	14	100.0
nightly_linux-aarch64_debug	2026-09-17	2026-09-02	14	14	100.0
Rci__nightly-connext_ubuntu_resolute_amd64	2026-09-17	2026-09-02	14	14	100.0
Rci__nightly-release_ubuntu_resolute_amd64	2026-09-16	2026-09-02	10	10	100.0
Rci__nightly-debug_ubuntu_resolute_amd64	2026-09-16	2026-09-02	11	11	100.0

The test fails because the RTI Connext license warning is unexpectedly written to stdout, causing the CLI test's empty-output assertion to fail.

Start with ros2lifecycle/test/test_cli.py and test_set_lifecycle_node_invalid_transition, where the empty-stdout assertion fails under rmw_connextdds. Reproduce the failing test in the referenced nightly job configuration and trace where the RTI Connext license warning enters the CLI process output. Done means the test passes without the unexpected license text in stdout.