Closed github-actions[bot] closed 3 months ago
Ros2 linux nighlies failed due to no space left in the device error.
I disconnected the agent and deleted all the big packages there
Reference build: https://build.osrfoundation.org/job/ros_gzharmonic_bridge-install-pkg_humble-ci-jammy-amd64/72/
Log output:
+ ros2 topic echo /chatter
Could not determine the type for the passed topic
Publishers [Address, Message Type]:
tcp://172.17.0.2:33719, gz.msgs.StringMsg
Subscribers [Address, Message Type]:
tcp://172.17.0.2:33719, gz.msgs.StringMsg
+ sleep 2
+ gz topic -t /chatter -m gz.msgs.StringMsg -p 'data:"Hello"'
+ grep -q Hello /tmp/echo_chatter
+ echo 'chatter log file does not contain the expected Hello string'
chatter log file does not contain the expected Hello string
+ exit 1
Build step 'Execute shell' marked build as failure
I ran the build again and it passed. Keeping track
Reference build: https://ci.ros2.org/view/nightly/job/nightly_win_rep/3368/
Error seems to be caused by Windows fatal exception: access violation
in launch_testing_ros and some SEH Access Violation
errors.
Keeping track
Reference build:
@Blast545 @clalancette these warnings are in different packages. Where should I report this?
Reference build: https://ci.ros2.org/view/nightly/job/nightly_win_rep/3371/
The failure is related to Windows fatal exception
and SEH Exception
in the test section.
SEH exception
shows the first time in "TestGoalRequestServer.send_result_rcl_errors" from "test_server" in rclcpp_action
package.
Windows fatal exception
shows the first time in test_message_filters_cache.py in message_filters
package.
SEH Exception happens before Windows fatal exception
Previous log #53