-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quiet a warning when CONNEXTDDS_DIR or NDDSHOME is not found. #158
Conversation
Failing to find those is an acceptable situation; in that case, we will end up just not building rmw_connextdds. Quiet the warning to only a STATUS message so it doesn't cause builds to go yellow. Signed-off-by: Chris Lalancette <clalancette@gmail.com>
Pulls: #158 |
Aarch64 is meant to fail, since we don't currently support Connext there. There is one failing test on Linux-rhel, but that is also expected right now (and happens on the nightlies). So going ahead and merging this one. |
@Mergifyio backport jazzy |
✅ Backports have been created
|
Failing to find those is an acceptable situation; in that case, we will end up just not building rmw_connextdds. Quiet the warning to only a STATUS message so it doesn't cause builds to go yellow. Signed-off-by: Chris Lalancette <clalancette@gmail.com> (cherry picked from commit c8ffbfd)
…161) Failing to find those is an acceptable situation; in that case, we will end up just not building rmw_connextdds. Quiet the warning to only a STATUS message so it doesn't cause builds to go yellow. Signed-off-by: Chris Lalancette <clalancette@gmail.com> (cherry picked from commit c8ffbfd) Co-authored-by: Chris Lalancette <clalancette@gmail.com>
Failing to find those is an acceptable situation; in that case, we will end up just not building rmw_connextdds. Quiet the warning to only a STATUS message so it doesn't cause builds to go yellow.
I found this while trying to run CI for ros2/ci#789, where the RHEL build goes yellow if we don't install Connext.