Skip to content

CI Periodically failing due to teardown issues with recent rolling/lyrical changes #6269

Description

@SteveMacenski

    [WARN] [1784161559.546415677] [rclcpp_lifecycle]: LifecycleNode is not shut down: Node still in state(1) in destructor
    Stack trace (most recent call last) in thread 6612:
    #17   Object "/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", at 0xffffffffffffffff, in 
    #16   Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7716c67187ab, in 
    #15   Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7716c66850d9, in 
    #14   Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.35", at 0x7716c6a4def8, in 
    #13   Object "/opt/overlay_ws/build/opennav_docking/test/test_docking_server_unit", at 0x5ec6ee84f600, in std::thread::_State_impl<std::thread::_Invoker<std::tuple<nav2::NodeThread::NodeThread(std::shared_ptr<rclcpp::node_interfaces::NodeBaseInterface>)::{lambda()#1}> > >::_M_run()
    #12   Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6d6835a, in rclcpp::executors::SingleThreadedExecutor::spin()
    #11   Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6d3713d, in rclcpp::Executor::get_next_executable(rclcpp::AnyExecutable&, std::chrono::duration<long, std::ratio<1l, 1000000000l> >)
    #10   Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6d36a42, in rclcpp::Executor::wait_for_work(std::chrono::duration<long, std::ratio<1l, 1000000000l> >)
    #9    Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6d1bac5, in 
    #8    Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6e28c90, in rclcpp::TimerBase::~TimerBase()
    #7    Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6d1bb89, in 
    #6    Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6e27914, in 
    #5    Object "/opt/ros/rolling/lib/librclcpp.so", at 0x7716c6e276b9, in 
    #4    Object "/opt/ros/rolling/lib/librcl.so", at 0x7716c62453c7, in 
    #3    Object "/opt/ros/rolling/lib/librcl.so", at 0x7716c6229fd5, in rcl_guard_condition_fini
    #2    Object "/opt/ros/rolling/lib/librmw_cyclonedds_cpp.so", at 0x7716c40c0feb, in rmw_destroy_guard_condition
    #1    Object "/opt/ros/rolling/lib/librmw_cyclonedds_cpp.so", at 0x7716c40c03c0, in 
    #0    Object "/opt/ros/rolling/lib/librmw_cyclonedds_cpp.so", at 0x7716c40bdbfe, in 

This has been periodically happening since the last 1-2 rolling syncs with releases trying to get out before the lyrical migration. This has been happening on my estimation of around ~20% of the time making our CI uncharacteristically flaky.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions