-
Notifications
You must be signed in to change notification settings - Fork 34
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
Initial OpenEmbedded Support for ROS 2 #168
Initial OpenEmbedded Support for ROS 2 #168
Conversation
Looks like the CI failure relates to the required dependencies. Please advise on the best way to proceed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a lot to review. Overall, this is looking like some major beefing up of superflore.
I'd like to make a few requests, though: since this change is so big, please refrain from small changes/refactors that don't deal with superflore supporting OE. I'm more than happy to review those separately, it just makes this diff really massive and hard to parse.
In addition, please @-mention some of the meta-ros people here, since I am not the right person to review that aspect of this.
Finally, thank you all for investing your time into this project! I'm beyond excited to see superflore continuing to expand and grow.
d4f6fae
to
2148ddc
Compare
@andre-rosa CI is running! 🎉 Unfortunately, the linter seems quite unhappy (though that's not too hard to fix usually). Other than linting, I think your Please also update the tests as needed, since you have reworked some of them (and thus some are no-longer valid). Thanks! |
1873151
to
2a2efa8
Compare
c477977
to
c75499f
Compare
@andre-rosa looks like there's some more tests to be updated. Look in Thanks! |
52bc23c
to
175d60c
Compare
@allenh1 << Thanks again for your review! All tests pass appropriately:
|
@andre-rosa I think that last commit should be a separate PR -- again, we have no limit on PRs, so make as many as you need to! I very much welcome them! But adding another release is not in the spirit of this PR, since it also affects Gentoo. I'll review the rest of this change set during the day tomorrow. Thanks again for all your work! |
a25ff19
to
175d60c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd still like this change set to be broken apart into a few more pieces, just so that we can keep better track of things in the git history (since I squash before merge).
I've suggested a next chunk to go for, and think that would be a good idea.
Otherwise, there's a few changes I've requested with the open embedded work.
Thanks again for your patience! I'm very excited to get these changes into superflore.
634f1d8
to
ce4779a
Compare
I'm going to need to take another look at most of it, since it's been a while, honestly. I'll try to do another full review at some point today. Note that we'll likely still need to pull chunks out. I'm also slightly concerned about a dip in coverage, but those can likely be fixed in post (with good faith they will be done).
That's good and all, but the merge button is blocked by the red CI. |
@andre-rosa must have been some fluke on the build server. Ran it four times in a row so I got concerned. Seems fine now. I'm going to do the review, then I'll have @tfoote give it a look, then we'll plan something going forward. |
@andre-rosa would you please run the following for me?
|
|
@andre-rosa you can skip that test if you want. |
|
@andre-rosa I'd really like to see a bit more coverage for
This PR reduces the total coverage of the repository by around 10%, which makes sense (since it's adding so many things). Do you think you could add some tests for that file? @tfoote do you have any opinions on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few things that stick out to me at the moment. I'm in favor of not dividing this more.
Definitely; will do it. |
Name Stmts Miss Cover Missing -------------------------------------------------------------------------------- superflore/generators/bitbake/oe_query.py 104 12 88% 58, 70, 121, 140-150, 154 ... -------------------------------------------------------------------------------- TOTAL 2065 1168 43%
@allenh1 << Thanks a bunch for reviewing! Please take another look.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. Thanks for all the patience with this patch!
@tfoote Please give this a look. |
Fixes #167 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pushing on this. This will be a great new capability to have.
* Unify dependency resolution between ebuild and bitbake * Point overlay meta repository to ros/meta-ros * Fix a exception when --skip-keys is not provided * Add build{tool}_export_depends to DEPENDS * Update DEPENDS format to OE recipe generation scheme rev 9 * Remove dependency groups handling * Add ROS_BPN to the generated recipes * Set DISTRO in generated-ros-distro.inc * Remove packagegroup-ros-world.bb as per OE recipe generation scheme rev 25 * Set ROS_SUPERFLORE_GENERATION_DATETIME to last-modified timestamp of distro cache * Bump rosdep dependency to >= 0.15.2 * Update comments as per OE recipe generation scheme rev 30 * Translate licenses * Add ROS_SUPERFLORE_GENERATED_RECIPES_FOR_COMPONENTS to rosdistro.conf * Filter out random branch name from the change summary
Initial OpenEmbedded support for superflore
https://github.com/lgsvl/build-ros2-lgsvl by the autogenerated ones, then build and run.
https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
Tagging @rojkov @bulwahn @johannesschrimpf @mpthompson @dkargin @dominiquehunziker @mdhorn << Could you please take a look?