methylDragon

> Whoops, I did not read the log correctly. Any idea what might call this error: > > ``` > $ ( source /home/runner/work/moveit2/moveit2/.work/upstream_ws/install/setup.bash && cd /home/runner/work/moveit2/moveit2/.work/target_ws && colcon test-result...

@sjahr Sorry to keep poking; is it possible to exclude the trajectory cache targets/tests from the humble CI? Or is there anything that I need to do on my end?

@sea-bass apologies for the delay. I've iterated on the PR and responded to/implemented all review comments!

Humble CI is failing tests (likely due to missing backports...) EDIT: Adding a mitigation...

> There is also a clang-tidy failure with the tf arg passed into restateInNewFrame() -- even though it's a shared pointer, it's asking to use const ref which is not...

> Sounds good. Also seeing `test_best_seen_execution_time_policy_with_move_group.cpp` failing in some jobs? Let me try with the latest commit. Let's see how CI responds.

> Ah, the 2nd run of CI failed in the rolling/clang-tidy job, actually. > > I'd be a bit wary of merging with these flaky tests. Any ideas on how...

> > It's the ros2_control_node itself that's getting a segfault though. I doubt this is related to moveit :/ > > Test is failing because ros2_control's node segfaults and returns...

> Seems the lingering flaky failures are now based on exit codes. You could consider trying something like this: > > [a401e13](https://github.com/moveit/moveit2/commit/a401e13f902e8a5b17ed40d7efdfcb535f7f1779) Hmm, okay. Less ideal since it feels like...

Oh man, let me continue investigating. Sorry for the repeated back and forths..