-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
I started investigating the valgrind test failures in CI, see for example in https://github.com/robotology/yarp-devices-ros2/actions/runs/8384433539/job/22993087127 .
Looking at the log, it seems that most of the failures are actually due to ROS2 itself, see ros2/rcl#1009 and ros2/rcutils#407 .
At this point, I guess the possible solutions are:
- either disable the valgrind test
- or add the ros2 failures to a valgrind suppression file, and use this suppression in all the valgrind tests
Metadata
Metadata
Assignees
Labels
No labels