As a ROS 2 developer, I have access to a report detailing potential regressions in the ROS 2 communication layer such as memory or concurrency related bugs. This report must be updated on
a regular basis (e.g. nightly) and should cover all ROS 2 communication packages (rmw* / rcl*).

Low-hanging fruits to close the gap between Linux, Mac OS X and Windows builds should be tackled. This will organically prevent regressions on Mac and Windows platform while improving developer productivity.

Owner: @ros2/aws-robotics

Exit Criteria

• The scripts and tools required to generate the report automatically are built and reviewed.
• The scripts are deployed and the report is generated automatically.
• The new system is adopted by the community. Reviewers monitor regressions and make rollback decisions based on the system output.

Tasks

• Add ASan sanitizer nightly job to ROS2 CI [ROS 2 QA] Add ASan sanitizer nightly job to ROS2 CI #665
• Add TSan sanitizer nightly job to ROS2 CI [ROS 2 QA] Add TSan sanitizer nightly job to ROS2 CI #666
• Add a CI job for Clang Linux nightly builds
• Implement PoC for Thread-Safety annotation [ROS2 QA] Implement PoC for Thread-Safety annotation #664