:farmer: check_msgs_launch_test failing in kilted by a python package not importing site module

[miguelgonrod]

Generated by Generative AI

No response

Operating System:

Ubuntu Noble

ROS version or commit hash:

Kilted

RMW implementation (if applicable):

rmw_zenoh, cyclonedds

RMW Configuration (if applicable):

No response

Client library (if applicable):

rclcpp

'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 test regressions

Expected behavior

To build without test regressions

Actual behavior

Building with test regressions

Additional information

Reference Builds

• Kci__nightly-zenoh_ubuntu_noble_amd64#109
• Kci__nightly-cyclonedds_ubuntu_noble_amd64#109

Failing Tests

• launch_testing_examples.launch_testing_examples.check_msgs_launch_test.launch_testing_examples.check_msgs_launch_test

Log Output

35: OK
35: [INFO] [python3-14]: sending signal 'SIGINT' to process[python3-14]
35: [python3-14] Fatal Python error: init_import_site: Failed to import the site module
35: [python3-14] Python runtime state: initialized
35: [python3-14] Traceback (most recent call last):
35: [python3-14]   File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
35: [python3-14]   File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
35: [python3-14]   File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
35: [python3-14]   File "<frozen importlib._bootstrap>", line 1176, in exec_module
35: [python3-14]   File "<frozen site>", line 643, in <module>
35: [python3-14]   File "<frozen site>", line 630, in main
35: [python3-14]   File "<frozen site>", line 413, in addsitepackages
35: [python3-14]   File "<frozen site>", line 242, in addsitedir
35: [python3-14]   File "<frozen site>", line 201, in addpackage
35: [python3-14]   File "<string>", line 1, in <module>
35: [python3-14]   File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
35: [python3-14]   File "<frozen importlib._bootstrap>", line 1322, in _find_and_load_unlocked
35: [python3-14]   File "<frozen importlib._bootstrap>", line 1262, in _find_spec
35: [python3-14]   File "<frozen importlib._bootstrap_external>", line 1528, in find_spec
35: [python3-14]   File "<frozen importlib._bootstrap_external>", line 1502, in _get_spec
35: [python3-14]   File "<frozen importlib._bootstrap_external>", line 1605, in find_spec
35: [python3-14]   File "<frozen importlib._bootstrap_external>", line 1648, in _fill_cache
35: [python3-14] KeyboardInterrupt
35: [ERROR] [python3-14]: process has died [pid 292555, exit code 1, cmd '/usr/bin/python3 -c 
35: import signal
35: import time
35: 
35: try:
35:     while True:
35:         time.sleep(1)
35: except KeyboardInterrupt:
35:     pass
35: '].
35: test_process_terminates_as_expected[garbage, rmw_zenoh_cpp] (rcl.TestRMWImplementationIDCheckAfterShutdown.test_process_terminates_as_expected[garbage, rmw_zenoh_cpp])
35: Test that the executable under test terminates as expected. ... ok

Flakyness 15 days

job_name	last_fail	first_fail	build_count	failure_count	failure_percentage
Kci__nightly-zenoh_ubuntu_noble_amd64	2026-03-31	2026-03-19	5	5	100.0
Kci__nightly-cyclonedds_ubuntu_noble_amd64	2026-03-31	2026-03-22	5	4	80.0
Rci__nightly-zenoh_ubuntu_noble_amd64	2026-03-30	2026-03-19	12	12	100.0

This error have been happenning for more than the jenkins history can save in memory, also even when it says 100% there are some builds that don't have this error.

CC: @Crola1702

[fujitatomoya]

this is not reproducible on rolling source build,

root@tomoyafujita-B760M-Pro-RS-D4:~/ros2_ws/colcon_ws# export RMW_IMPLEMENTATION=rmw_cyclonedds_cpp
root@tomoyafujita-B760M-Pro-RS-D4:~/ros2_ws/colcon_ws# colcon test --event-handlers console_direct+ --packages-select launch_testing_examples --pytest-args launch_testing_examples/check_msgs_launch_test.py
Starting >>> launch_testing_examples
============================= test session starts ==============================
platform linux -- Python 3.12.3, pytest-7.4.4, pluggy-1.4.0
cachedir: /root/ros2_ws/colcon_ws/build/launch_testing_examples/.pytest_cache
rootdir: /root/ros2_ws/colcon_ws/src/ros2/examples/launch_testing/launch_testing_examples
configfile: setup.cfg
plugins: launch-testing-ros-0.29.6, launch-testing-3.9.6, ament-mypy-0.20.3, ament-xmllint-0.20.3, ament-copyright-0.20.3, ament-pep257-0.20.3, ament-flake8-0.20.3, ament-lint-0.20.3, anyio-4.11.0, None-None, typeguard-4.1.5, timeout-2.2.0, cov-4.1.0, rerunfailures-12.0, mock-3.12.0, colcon-core-0.20.1
collecting ...
collected 1 item

launch_testing_examples/check_msgs_launch_test.py .                      [100%]

- generated xml file: /root/ros2_ws/colcon_ws/build/launch_testing_examples/pytest.xml -
============================== 1 passed in 1.33s ===============================
Finished <<< launch_testing_examples [1.97s]

Summary: 1 package finished [2.83s]

@miguelgonrod is this only happening to kilted? or do we have similar failure with rolling?

[miguelgonrod]

Hi Fujita, looking at flakyness it is also happening in rolling

job_name	last_fail	first_fail	build_count	failure_count	failure_percentage
Kci__nightly-cyclonedds_ubuntu_noble_amd64	2026-04-07	2026-03-25	5	5	100.0
Kci__nightly-zenoh_ubuntu_noble_amd64	2026-04-04	2026-03-25	4	4	100.0
Rci__nightly-zenoh_ubuntu_noble_amd64	2026-03-30	2026-03-23	8	8	100.0

https://build.ros2.org/job/Rci__nightly-zenoh_ubuntu_noble_amd64/386 this one was the last one that failed in rolling (Don't check the jobs after that, they failed by a pyqtbindings thing)

but in rolling looks like a different problem

----------------------------- Captured stderr call -----------------------------
test_check_if_msgs_published (launch_testing_examples.check_msgs_launch_test.TestFixture.test_check_if_msgs_published) ... [WARN] [1774887026.043728411] [rmw_zenoh_cpp]: Unable to connect to a Zenoh router. Have you started a router with `ros2 run rmw_zenoh_cpp rmw_zenohd`?
[WARN] [1774887026.043746604] [rmw_zenoh_cpp]: Unable to connect to a Zenoh router after 1 attempt(s). Please ensure that a Zenoh router is running and can be reached. You may increase the number of attempts to check for a router by setting the ZENOH_ROUTER_CHECK_ATTEMPTS environment variable. Proceeding with initialization but other peers will not discover or receive data from peers in this session until a router is started.
ERROR

======================================================================
ERROR: test_check_if_msgs_published (launch_testing_examples.check_msgs_launch_test.TestFixture.test_check_if_msgs_published)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/ws/src/ros2/examples/launch_testing/launch_testing_examples/launch_testing_examples/check_msgs_launch_test.py", line 43, in test_check_if_msgs_published
    with WaitForTopics([('chatter', String)], timeout=15.0):
  File "/tmp/ws/install_isolated/launch_testing_ros/lib/python3.12/site-packages/launch_testing_ros/wait_for_topics.py", line 143, in __enter__
    raise RuntimeError('Did not receive messages on these topics: ',
RuntimeError: ('Did not receive messages on these topics: ', {'chatter'})

----------------------------------------------------------------------