[BUG] Cancellation test rejects permitted forced descendant retirement #179

Closed
opened 2026-10-23 19:42:02 +02:00 by erikinkinen · 2 comments
Owner

Summary

The Boot-tool cancellation test requires a detached descendant to exit from
SIGTERM. The native owner may instead retire that child with SIGKILL after its
leader has exited. This valid outcome causes an intermittent host-suite failure.

Reproduction

Run boot_tool_owned_producer_test.py at Integration
8501d3f52a8ae6019c9db9572da3c9577fab49f5. The real cancellation case creates a
leader and detached child, then closes the original cancellation writer after
the child's readiness record. CI 2954 records descendant_statuses: [-9] where
the assertion expects [-15].

Expected and actual behavior

The test should require original socket EOF, complete native retirement and the
original cancellation status, while accepting either permitted terminal signal
for the detached child. Instead, it fails solely because SIGKILL was used.

The owner first sends group SIGTERM. It sends SIGTERM to adopted children while
the leader is still live, then uses SIGKILL for remaining adopted children after
reaping the leader. A detached child can reach adoption only in that final stage.

Environment and identity

Linux x86-64 CI runner; the revision above; Python host shard one. The owner and
its existing grace intervals are unchanged. The same test passed in CI 2951;
that result does not make either native schedule mandatory.

Evidence and prior checks

CI 2954 retains the
exact [-9] != [-15] assertion. The failure occurs after the socket EOF and
original leader-status checks pass. The test has not yet reached its subsequent
cleanup-field assertions in that failing run; those fields are not inferred.

Tracking

Related: cancellation fixture
and PR 12.

  • Retain the failing native outcome and identify the schedule-dependent assertion.
  • Accept both permitted signals while preserving all custody, EOF and error checks.
  • Add a real detached child that ignores SIGTERM and requires forced retirement.
  • Pass the affected host suite in CI.
## Summary The Boot-tool cancellation test requires a detached descendant to exit from SIGTERM. The native owner may instead retire that child with SIGKILL after its leader has exited. This valid outcome causes an intermittent host-suite failure. ## Reproduction Run `boot_tool_owned_producer_test.py` at Integration `8501d3f52a8ae6019c9db9572da3c9577fab49f5`. The real cancellation case creates a leader and detached child, then closes the original cancellation writer after the child's readiness record. CI 2954 records `descendant_statuses: [-9]` where the assertion expects `[-15]`. ## Expected and actual behavior The test should require original socket EOF, complete native retirement and the original cancellation status, while accepting either permitted terminal signal for the detached child. Instead, it fails solely because SIGKILL was used. The owner first sends group SIGTERM. It sends SIGTERM to adopted children while the leader is still live, then uses SIGKILL for remaining adopted children after reaping the leader. A detached child can reach adoption only in that final stage. ## Environment and identity Linux x86-64 CI runner; the revision above; Python host shard one. The owner and its existing grace intervals are unchanged. The same test passed in CI 2951; that result does not make either native schedule mandatory. ## Evidence and prior checks [CI 2954](https://git.erikinkinen.fi/erix/integration/actions/runs/2954) retains the exact `[-9] != [-15]` assertion. The failure occurs after the socket EOF and original leader-status checks pass. The test has not yet reached its subsequent cleanup-field assertions in that failing run; those fields are not inferred. ## Tracking Related: [cancellation fixture](https://git.erikinkinen.fi/erix/integration/issues/174) and [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12). - [x] Retain the failing native outcome and identify the schedule-dependent assertion. - [x] Accept both permitted signals while preserving all custody, EOF and error checks. - [x] Add a real detached child that ignores SIGTERM and requires forced retirement. - [x] Pass the affected host suite in CI.
Author
Owner

Published 5eed43c1.

The test now accepts either permitted terminal signal for the detached child and keeps its socket EOF, original cancellation status and complete native custody checks. A new real child ignores SIGTERM and must be retired with SIGKILL. All 15 producer controls pass, including the cold offline build and source/error negatives; no warnings were emitted.

The native owner and its grace intervals are unchanged. The original CI failure is retained; the new CI result is pending.

Published [5eed43c1](https://git.erikinkinen.fi/erix/integration/commit/5eed43c1c0931740f1fe7719eaacdffa3a261445). The test now accepts either permitted terminal signal for the detached child and keeps its socket EOF, original cancellation status and complete native custody checks. A new real child ignores SIGTERM and must be retired with SIGKILL. All 15 producer controls pass, including the cold offline build and source/error negatives; no warnings were emitted. The native owner and its grace intervals are unchanged. The original CI failure is retained; the new CI result is pending.
Author
Owner

Fixed in 5eed43c1. The fixture accepts both permitted terminal signals while retaining the socket EOF, original cancellation status and complete cleanup checks. It also covers a detached child that ignores SIGTERM.

Run 2963 passes both host shards: 201 modules and 2,229 cases, including all 15 Boot-tool producer cases. Closing this regression.

Fixed in [5eed43c1](https://git.erikinkinen.fi/erix/integration/commit/5eed43c1). The fixture accepts both permitted terminal signals while retaining the socket EOF, original cancellation status and complete cleanup checks. It also covers a detached child that ignores SIGTERM. [Run 2963](https://git.erikinkinen.fi/erix/integration/actions/runs/2963) passes both host shards: 201 modules and 2,229 cases, including all 15 Boot-tool producer cases. Closing this regression.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:21 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#179
No description provided.