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

Noetic changelogs and version bump (1.1.2) #2423

Closed
wants to merge 2 commits into from

Conversation

tylerjw
Copy link
Member

@tylerjw tylerjw commented Nov 20, 2020

Description

Changelogs and version bump for Noetic release 1.1.2

@codecov
Copy link

codecov bot commented Nov 20, 2020

Codecov Report

Merging #2423 (43218e3) into master (eca2deb) will increase coverage by 0.09%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2423      +/-   ##
==========================================
+ Coverage   60.47%   60.55%   +0.09%     
==========================================
  Files         351      351              
  Lines       26434    26462      +28     
==========================================
+ Hits        15982    16021      +39     
+ Misses      10452    10441      -11     
Impacted Files Coverage Δ
moveit_ros/manipulation/pick_place/src/pick.cpp 68.94% <0.00%> (-9.70%) ⬇️
moveit_ros/moveit_servo/src/pose_tracking.cpp 41.35% <0.00%> (-5.01%) ⬇️
moveit_core/planning_scene/src/planning_scene.cpp 58.01% <0.00%> (+0.11%) ⬆️
...raint_samplers/src/default_constraint_samplers.cpp 82.25% <0.00%> (+0.37%) ⬆️
...dl_kinematics_plugin/src/kdl_kinematics_plugin.cpp 76.55% <0.00%> (+0.45%) ⬆️
moveit_ros/manipulation/pick_place/src/place.cpp 70.14% <0.00%> (+0.70%) ⬆️
...anning/planning_pipeline/src/planning_pipeline.cpp 69.02% <0.00%> (+7.05%) ⬆️
...g_request_adapter/src/planning_request_adapter.cpp 67.57% <0.00%> (+8.11%) ⬆️
.../ompl_interface/src/detail/constrained_sampler.cpp 65.72% <0.00%> (+22.86%) ⬆️
...r_plugins/src/fix_start_state_path_constraints.cpp 86.49% <0.00%> (+54.06%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eca2deb...43218e3. Read the comment docs.

Copy link
Contributor

@felixvd felixvd left a comment

Choose a reason for hiding this comment

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

LGTM, but why does Travis fail on clang?

@rhaschke
Copy link
Contributor

We didn't had a single successful master branch build on Travis since 18 days, namely since the Pilz planner (#1893) was merged!
The core reason is that we are running out of build time - exactly what I predicted before!
Even worse, Travis has changed it's pricing model: https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing.
Currently, all CI jobs are disabled, because we already consumed all our free credits. @davetcoleman we need to discuss urgently, how to mitigate this issue.

Additionally, there is a flaky unit test:

build/moveit_ros_planning_interface/test_results/moveit_ros_planning_interface/rosunit-move_group_pick_place_test.xml: 2 tests, 0 errors, 2 failures, 0 skipped
Summary: 1618 tests, 0 errors, 2 failures, 2 skipped

@tylerjw
Copy link
Member Author

tylerjw commented Nov 21, 2020

I started debugging the test that is flaky yesterday but don't have a fix for it. Some testing yesterday showed that that notice on Travis is not telling the truth and it is running ci (for now atleast). I have started working on circleci and am using GitHub actions on one customer project. I have yet to get better performance out of circleci and wouldn't recommend it yet. GitHub actions seems to be faster than Travis (Microsoft might be throwing money at more powerful machines to try to get people to switch). To use GitHub actions the easiest way will be to use industrial_ci. There are a handful of things we have in moveit_ci that we would lose until we get those things upstreamed. One of them is code coverage which is almost in industrial_ci.

Another decision we should consider is (grasp) breaking up the repo. One sort of obvious thing we could factor out is anything that depends on qt. That would make for faster builds and have the advantage that people who depend on moveit but don't want the qt stuff but don't have them on their target can stop having to deal with our qt dependency.

On top of all this the noetic fcl thing isn't building and causing problems for the official buildfarm.

@rhaschke
Copy link
Contributor

I started debugging the test that is flaky yesterday but don't have a fix for it.

What's the culprit?

On top of all this the noetic fcl thing isn't building and causing problems for the official buildfarm.

Can you provide any evidence, e.g. a link to a buildfarm build?

@tylerjw
Copy link
Member Author

tylerjw commented Nov 22, 2020

ros/rosdistro#27401

@tylerjw
Copy link
Member Author

tylerjw commented Nov 22, 2020

I started debugging the test that is flaky yesterday but don't have a fix for it.

What's the culprit?

I don't know yet.

@jschleicher
Copy link
Contributor

jschleicher commented Nov 23, 2020

We didn't had a single successful master branch build on Travis since 18 days, namely since the Pilz planner (#1893) was merged!

@rhaschke The PR builds before the merge did succeed. But the check takes veeryy long:
grafik

Is moveit/moveit_ci#73 still active? It seems like clang-tidy runs on all files (again) - while no files changed in the current PR?

@tylerjw
Copy link
Member Author

tylerjw commented Nov 23, 2020

Picknik now paying for the 1 runner plan on Travis to have a temporary solution to the timeouts. This will probably make CI take longer but not timeout. In the long-ish term I will be investigating the other providers and doing work to support them to try to find a better solution than Travis.

@tylerjw tylerjw closed this Nov 23, 2020
@tylerjw tylerjw reopened this Nov 23, 2020
@rhaschke
Copy link
Contributor

rhaschke commented Dec 9, 2020

@tylerjw: The ROS build farm is complaining about missing pilz packages, e.g.: moveit_resources_prbt_moveit_config
http://build.ros.org/job/Ndev__moveit__ubuntu_focal_amd64/20/display/redirect

Didn't you already release those?

@jschleicher
Copy link
Contributor

@tylerjw It seems, there hasn't been a release of ros-planning/moveit_resources since october?!

@tylerjw
Copy link
Member Author

tylerjw commented Jan 8, 2021

I remember releasing moveit_resources when I did the last noetic release. It appears I didn't though. We should release it so the build farm is happy.

This was referenced Jan 8, 2021
@jschleicher
Copy link
Contributor

jschleicher commented Jan 12, 2021

@tylerjw actually this PR (#2423) ist still open, so neiter the november moveit release nor the release of moveit_resources got bloomed? When do you plan to do the release? Or are there any blocker(s)?

@tylerjw
Copy link
Member Author

tylerjw commented Jan 12, 2021

@jschleicher I am planning on doing a release once some of the tests become more robust. With the current state of our runners on travis the move_group interface test and subframes test has become flaky. I'm working with @bostoncleek to get that resolved so it stops blocking the OMPL constrained space PR and many others. I'm hoping that we'll have a solution for that within the next couple weeks.

@tylerjw tylerjw added this to Low priority in MoveIt & Co Jan 13, 2021
@tylerjw tylerjw self-assigned this Jan 13, 2021
@jschleicher
Copy link
Contributor

@tylerjw We're still waiting for a binary release including the pilz_industrial_motion_planner. Is there any news on your side?

within the next couple weeks.

@tylerjw
Copy link
Member Author

tylerjw commented Apr 9, 2021

closing this as 1.1.2 just went out

@tylerjw tylerjw closed this Apr 9, 2021
MoveIt & Co automation moved this from Low priority to Closed Apr 9, 2021
@v4hn v4hn moved this from Closed to Low priority in MoveIt & Co Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
MoveIt & Co
  
Low priority
Development

Successfully merging this pull request may close these issues.

None yet

5 participants