Pilz integration tests have started failing sporadically on Rolling due to exit code -11

[sea-bass]

Description

There have lately been pretty frequent (~50% or so) flakes with some exit codes in Pilz integration tests:
https://github.com/moveit/moveit2/actions/runs/12589290424/job/35088819135?pr=3187#step:11:8621

    ======================================================================
    FAIL: test_exit_codes (pilz_industrial_motion_planner.TestOutcome.test_exit_codes)
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "/home/runner/work/moveit2/moveit2/.work/target_ws/src/moveit2/moveit_planners/pilz_industrial_motion_planner/test/unit_tests/launch/unittest_planning_context_loaders.test.py", line 53, in test_exit_codes
        launch_testing.asserts.assertExitCodes(
      File "/opt/ros/rolling/lib/python3.12/site-packages/launch_testing/asserts/assert_exit_codes.py", line 62, in assertExitCodes
        assert info.returncode in allowable_exit_codes, 'Proc {} exited with code {}'.format(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    AssertionError: Proc unittest_planning_context_loaders-1 exited with code -11

This seems to be specifically happening in the rolling CI jobs, but it's usually cleared away after 1 or 2 retries.

Creating this issue to keep track.

ROS Distro

Rolling

OS and version

Ubuntu 24.04

Source or binary build?

Source

If binary, which release version?

No response

If source, which branch?

No response

Which RMW are you using?

None

Steps to Reproduce

Run CI

Expected behavior

CI is green

Actual behavior

CI is not always green

Backtrace or Console output

No response