-
Notifications
You must be signed in to change notification settings - Fork 612
Remove source builds of geometric_shapes
and srdfdom
#3233
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #3233 +/- ##
==========================================
- Coverage 45.88% 42.13% -3.75%
==========================================
Files 717 704 -13
Lines 62575 57809 -4766
Branches 7565 7566 +1
==========================================
- Hits 28706 24351 -4355
+ Misses 33703 31859 -1844
- Partials 166 1599 +1433 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Bleh. This error seems familiar but I forget what it was.
Update: Ended up ignoring it, and it makes CI pass, but unclear whether this is right. |
Maybe we hold off on this until moveit/geometric_shapes#258 is released as well? |
This is annoying. Seems that the coverage tool has analyzed files in Is there a better way to clear out this state that doesn't lead to ignoring all missing source code errors? |
Since it's the code coverage tool, I think the only way to reset the cache of what it is comparing against is to merge the PR (when we merge, it will run the CI, and then that is the new baseline that all PRs are compared against) |
(cherry picked from commit eb8bfdc)
(cherry picked from commit eb8bfdc) Co-authored-by: Sebastian Castro <[email protected]>
Description
We had added these a few months back to circumvent some breakages, but this should no longer be needed.
Q: Should we backport this to Jazzy? Because if so,
srdfdom
there is at 2.0.5 and not 2.0.7, so I think we may need to first release to there. But I also forget whether thesrdfdom
version was actually a problem in Jazzy, or it was just Rolling. I guess it's worth just testing the backport?(self-answer): I just pushed
srdfdom
2.0.7 releases to humble and jazzy on rosdistro.Checklist