Restore Connext 7.7 and apply feedback#860
Conversation
|
This looks a LOT better. We're even passing the cross-vendor tests with Fast-DDS on Linux. Windows is still seeing some failures in |
|
We can work on that issue during the stabilization period. The failing tests don't seem really blocking, as the more important ones are passing, and Linux looks really good. Do we need the bigger validation (like the one we got yesterday with the smoke tests for Linux) to get this merged? It seems that most of the issues are now gone and the tests failing look hard to reproduce (as they only happen on Windows). |
That's what the |
|
@cottsay From my side everything looks good. Please feel free to proceed with the merge if the Windows build is stable. From RTI, we are committed to supporting the stabilization process in case any additional issues arise, not only related to Connext or the RMW. As we continue gaining a deeper understanding of the ROS 2 CI and overall project, we are increasingly in a position to help across more areas. Thanks for your support and assistance. |
|
@cottsay I think the test failures in |
Description
Yesterday we were facing an issue with Connext 7.7.0 integration for Lyrical. See ros2/rmw_connextdds#219 for the full discussion.
This pull request re-introduces Connext 7.7.0 in the CI for Lyrical removed in #859, along with minor fixes to Windows builds (see #844 (comment)).
We need a validation using this branch (
fgallegosalido/fix/843-update-rti-connext) for the CI and the branchfeature/218-update-connext-770from ros2/rmw_connextdds#219.Is this user-facing behavior change?
The CI will now use Conenxt 7.7.0 for Lyrical.
Did you use Generative AI?
No
Additional Information
For more information about what was causing the issues related to Connext 7.7.0, see ros2/rmw_connextdds#219 (comment).