Skip to content

ci_agent in build.ros2.org has unexpected running nodes in background and causes test regressions #11

@Crola1702

Description

@Crola1702

Migrated from https://github.com/osrf/buildfarmer/issues/337 on Aug 22, 2022

Description

3 unexpected nodes in this agent are causing test regressions on Humble

Reference builds:

Failing tests:

Details

Example test

Test: rcl.TestGetNodeNames__rmw_fastrtps_cpp.test_rcl_get_node_names (from TestGetNodeNames__rmw_fastrtps_cpp)
Stacktrace:

/tmp/ws/src/ros2/rcl/rcl/test/rcl/test_get_node_names.cpp:138
Expected equality of these values:
  discovered_nodes
    Which is: { ("demo_node_0", "/"), ("demo_node_1", "/"), ("demo_node_2", "/"), ("node1", "/"), ("node1", "/"), ("node2", "/"), ("node2", "/ns/ns"), ("node3", "/ns") }
  expected_nodes
    Which is: { ("node1", "/"), ("node1", "/"), ("node2", "/"), ("node2", "/ns/ns"), ("node3", "/ns") }

There are 3 unexpected nodes on this test: demo_node_0, demo_node_1, and demo_node_2.

Explanation

  • We tracked errors throughout the log and found test were failing because of 3 nodes that appeared to be created since the start of the build
  • We tried to replicate this error in ci.ros2.org: Build Status
  • As we couldn't replicate the error in ci.ros2.org we think this agent had issues destroying those 3 nodes.
  • We think this error may be related to processes not being closed after a failure (even with Docker).

22/08 Update

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