Skip to content
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

Foxy backport: Fix target_link_directories/link_directories in cmake (#29) #32

Merged
merged 1 commit into from
Feb 26, 2021

Conversation

clalancette
Copy link
Contributor

Signed-off-by: ahcorde ahcorde@gmail.com

Otherwise, Foxy fails to build on Ubuntu 18.04.

Copy link
Contributor

@ahcorde ahcorde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mind to sign the commit ?

@clalancette
Copy link
Contributor Author

Do you mind to sign the commit ?

Oops, yeah, good point. Will do.

Signed-off-by: ahcorde <ahcorde@gmail.com>
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@clalancette
Copy link
Contributor Author

There we go, DCO bot is happier now.

@clalancette
Copy link
Contributor Author

clalancette commented Feb 12, 2021

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@clalancette
Copy link
Contributor Author

@jacobperron Both Linux CIs have failing tests in sros2, macOS has a small set of failures, and Windows has an even larger set of failures. It seems pretty unlikely to me that any of these test failures were caused by this PR, but could you take a quick look? Thanks.

@jacobperron
Copy link
Member

jacobperron commented Feb 12, 2021

The last time I recall running a full CI for Foxy was in December: ros2/ros2#1070
I've seen the sros2 and laser_geometry test failures before, but the ros2doctor failure on macOS and the others on Windows look new to me. I agree that it seems unlikely that this PR would cause those to start failing. It's possible something else changed that is causing those to fail. Maybe it's a good time to trigger a full Foxy build to see where our baseline is now.

@jacobperron
Copy link
Member

Maybe it's a good time to trigger a full Foxy build to see where our baseline is now.

Here we go: ros2/ros2#1090

@clalancette
Copy link
Contributor Author

Here we go: ros2/ros2#1090

Thanks, appreciated. I'll make a decision on whether to merge this PR once those results come back.

@clalancette clalancette changed the title Fix target_link_directories/link_directories in cmake (#29) Foxy backport: Fix target_link_directories/link_directories in cmake (#29) Feb 16, 2021
@clalancette
Copy link
Contributor Author

Hm. Well, while there is a bunch of overlap between the CI job here and the one that Jacob pointed to, it's not 100%. There are some failures here that are not in the unmodified job. I still think it is unlikely that this change is the cause of those failures, but I'll hold off on merging this for now.

@clalancette
Copy link
Contributor Author

I'm going to go ahead and merge this regardless of the warnings. I highly doubt it is because of this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants