Closed github-actions[bot] closed 5 months ago
Reference builds:
Test regressions:
Log output:
test/test_daemon.py:209: in test_get_publishers_info_by_topic
publishers_info = daemon_node.get_publishers_info_by_topic(TEST_TOPIC_NAME)
/usr/lib/python3.10/xmlrpc/client.py:1122: in __call__
return self.__send(self.__name, args)
/usr/lib/python3.10/xmlrpc/client.py:1464: in __request
response = self.__transport.request(
/usr/lib/python3.10/xmlrpc/client.py:1166: in request
return self.single_request(host, handler, request_body, verbose)
/usr/lib/python3.10/xmlrpc/client.py:1182: in single_request
return self.parse_response(resp)
/usr/lib/python3.10/xmlrpc/client.py:1354: in parse_response
return u.close()
/usr/lib/python3.10/xmlrpc/client.py:668: in close
raise Fault(**self._stack[0])
E xmlrpc.client.Fault: <Fault 1: "<class 'AttributeError'>:'TypeHash' object has no attribute '__slots__'">
It's probably related to a change in https://github.com/ros2/ros2cli/commit/64d216cb8fafef83d046b79ee6294afb06b7c595
No, it was this PR: https://github.com/ros2/rclpy/pull/1232
Which has now been reverted: https://github.com/ros2/rclpy/pull/1243
Note There is an interesting kind of wrong behaviour in the buildfarm script. Every script uses the
%...%
syntax, this means short error names can be also confused with big error names (that's what's happening with rclcpp.test_timer and rclcpp.test_timers_manager)
Reference build:
Reference builds:
Test regression: demo_nodes_cpp.TestExecutablesTutorial.test_processes_output\
Log output:
Traceback (most recent call last):
File "C:\ci\ws\build\demo_nodes_cpp\test_use_logger_service__rmw_connextdds_Release.py", line 74, in test_processes_output
proc_output.assertWaitFor(
File "C:\ci\ws\install\Lib\site-packages\launch_testing\io_handler.py", line 146, in assertWaitFor
assert success, 'Waiting for output timed out'
AssertionError: Waiting for output timed out
Flaky ratio stats:
job_name | last_fail | first_fail | build_count | failure_count | failure_percentage |
---|---|---|---|---|---|
nightly_win_rep | 2024-03-12 | 2024-02-27 | 15 | 15 | 100.0 |
nightly_win_deb | 2024-03-10 | 2024-02-27 | 13 | 6 | 46.15 |
nightly_linux-aarch64_repeated | 2024-03-02 | 2024-03-02 | 16 | 1 | 6.25 |
nightly_linux-rhel_repeated | 2024-02-29 | 2024-02-29 | 16 | 1 | 6.25 |
Reference build: https://ci.ros2.org/view/nightly/job/nightly_win_rel/2982/
(also happening in Ici_connext and Hci_connext)
Test regression: launch_testing_ros.test.examples.check_node_launch_test.check_node_launch_test
Log output:
FAIL: check_node_launch_test.TestFixture.test_node_start
-----------------------------------------------------------------------------------------------------------------------------
Traceback (most recent call last):
File "C:\ci\ws\src\ros2\launch_ros\launch_testing_ros\test\examples\check_node_launch_test.py", line 71, in test_node_start
assert found, 'Node not found!'
AssertionError: Node not found!
assert False
Flaky ratio stats:
job_name | last_fail | first_fail | build_count | failure_count | failure_percentage |
---|---|---|---|---|---|
nightly_win_rel | 2024-03-12 | 2024-03-02 | 15 | 9 | 60.0 |
Hci__nightly-connext_ubuntu_jammy_amd64 | 2024-03-12 | 2024-02-27 | 6 | 5 | 83.33 |
nightly_linux-rhel_repeated | 2024-03-10 | 2024-03-10 | 16 | 1 | 6.25 |
Ici__nightly-connext_ubuntu_jammy_amd64 | 2024-03-10 | 2024-02-28 | 4 | 4 | 100.0 |
nightly_linux_repeated | 2024-03-08 | 2024-03-08 | 16 | 1 | 6.25 |
nightly_win_rep | 2024-03-01 | 2024-03-01 | 15 | 1 | 6.67 |
Reference build:
Test regressions:
Log output:
test/test_ros2trace/test_trace.py:312: in test_env_var_ros_home
self.assertEqual(0, ret)
E AssertionError: 0 != 1
test/test_ros2trace/test_trace.py:289: in test_env_var_ros_trace_dir
self.assertEqual(0, ret)
E AssertionError: 0 != 1
Flaky ratio stats:
job_name | last_fail | first_fail | build_count | failure_count | failure_percentage |
---|---|---|---|---|---|
nightly_linux-aarch64_release | 2024-03-12 | 2024-02-26 | 16 | 8 | 50.0 |
nightly_linux-aarch64_debug | 2024-03-12 | 2024-03-02 | 16 | 4 | 25.0 |
nightly_linux_debug | 2024-03-10 | 2024-03-04 | 16 | 4 | 25.0 |
nightly_linux_release | 2024-03-09 | 2024-02-26 | 16 | 5 | 31.25 |
nightly_linux-rhel_release | 2024-03-08 | 2024-03-05 | 16 | 2 | 12.5 |
nightly_linux-rhel_debug | 2024-02-29 | 2024-02-29 | 15 | 1 | 6.67 |
Reference build: https://ci.ros2.org/view/nightly/job/nightly_win_deb/3031/
Test regressions:
Log output (failure):
cpplint_rosidl_generated_cpp ......................***Timeout 120.02 sec
On the builds before the change to sequential executor, there was no timeout (build 3012):
cpplint_rosidl_generated_cpp ...................... Passed 84.45 sec
Reported in: https://github.com/ros2/rosidl/issues/790
Can't surely tell when it started, at least given that debbuilder logs include jobs for each different OS.
Reference build today: https://build.osrfoundation.org/job/gz-tools2-debbuilder/1492/ Oldest reference build: March 5th: https://build.osrfoundation.org/job/gz-tools2-debbuilder/1466/console
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) gz-tools2-build-deps:amd64 < 2.0.0+nightly+git20240314+1r0503f899ba24e7979906fbc9ee774d515d7147f4-1~focal @iU mK Nb Ib >
Broken gz-tools2-build-deps:amd64 Depends on libgz-cmake4-dev:amd64 < none @un H >
Removing gz-tools2-build-deps:amd64 because I can't find libgz-cmake4-dev:amd64
Pinging gazebo team, it seems there's a missing release of gz-cMake4 somewhere
Previous log #31