Fix failing test on rolling#416
Conversation
matthew-reynolds
left a comment
There was a problem hiding this comment.
See #406 (comment) for a potential way to avoid duplication of the whole test suite instantiation.
|
Thanks @matthew-reynolds I think this definitely looks way better! @bmagyar @Karsten1987 I think this should be ready to merge. |
tylerjw
left a comment
There was a problem hiding this comment.
I tested this locally on rolling and it works for me.
|
Thanks guys! |
|
Did anybody test this on OSX? This still fails for the exact same reason locally for me as before. |
😢 I don't think any of us have an OSX setup to test on. We had assumed this would work because the #define should work the same way it did before on osx. Is APPLE not the right name to test for? |
|
The problem is the |
|
I think a good way to test it would be setup a CI for OSX. I have no way of testing this but I assumed the |
|
Also, come to think about this. I don't think dividing it via OS is the right approach here in the first place. The issue is that macros are defined differently depending on the gtest version. That gtest version might get updated on OSX as well in future ROS versions. So we'd have to address this |
|
@Karsten1987 I think OSX was dropped to Tier3 from Galactic & onwards You just said that the gtest version may be different on osx even in foxy, why not try an if based on the gtest version? Worst case we can inject it via the cmake on compilation |
Fixes the failin rolling test with a specfic macro for MacOS devices. See #406 and #390 .
This will allow ros2_control to compile on rolling