[BUG] Blocked-sink clock test can expire before sink entry #477

Open
opened 2026-11-06 22:42:45 +01:00 by erikinkinen · 0 comments
Owner

Summary

The blocked-output cancellation test can fail before it reaches the behavior it intends to test. This intermittently blocks the Rust CI job even when native cancellation and cleanup assertions pass.

Reproduction

Run owned_command_caller_clock_test.py through unittest discovery with the normal explicit fixture storage. The affected case is test_actual_caller_timeout_unwinds_a_blocked_live_sink.

The failure was observed in the Rust check for #474, job 62804. It is intermittent; a deterministic local reproduction has not been established.

Expected and actual behavior

The test should establish that the live output sink has been entered, then demonstrate asynchronous caller cancellation while that write is blocked.

The observed run passed the native TERM and cleanup assertions but failed when reading the absent sink-entered marker. GNU timeout starts its 0.3-second clock before the inner interpreter and native command are ready. Expiry during startup is a suspected explanation, not a proven native-owner defect.

Environment and identity

  • Integration revision: bd983dc4e479400734b1d168bf060c90e30e3c92.
  • Host-side Python test using GNU timeout; no guest image is involved.
  • The outer test retains its 10-second hard and 5-second quiet limits.
  • Last known working revision: not established.

Evidence and prior checks

The affected source case uses the same timeout helper as the fractional TERM, minute-suffixed HUP and disabled-clock cases. Their coverage must remain intact.

Tracking

  • Establish readiness through genuine child custody before measuring the blocked-write cancellation interval.
  • Preserve asynchronous interruption, exact signal status and native cleanup assertions.
  • Keep the existing interval and enclosing limits; do not replace the test with immediate self-signalling or a longer timeout.
  • Demonstrate the corrected case in CI.
## Summary The blocked-output cancellation test can fail before it reaches the behavior it intends to test. This intermittently blocks the Rust CI job even when native cancellation and cleanup assertions pass. ## Reproduction Run `owned_command_caller_clock_test.py` through unittest discovery with the normal explicit fixture storage. The affected case is `test_actual_caller_timeout_unwinds_a_blocked_live_sink`. The failure was observed in the Rust check for [#474](https://git.erikinkinen.fi/erix/integration/pulls/474), job 62804. It is intermittent; a deterministic local reproduction has not been established. ## Expected and actual behavior The test should establish that the live output sink has been entered, then demonstrate asynchronous caller cancellation while that write is blocked. The observed run passed the native TERM and cleanup assertions but failed when reading the absent `sink-entered` marker. GNU timeout starts its 0.3-second clock before the inner interpreter and native command are ready. Expiry during startup is a suspected explanation, not a proven native-owner defect. ## Environment and identity - Integration revision: `bd983dc4e479400734b1d168bf060c90e30e3c92`. - Host-side Python test using GNU timeout; no guest image is involved. - The outer test retains its 10-second hard and 5-second quiet limits. - Last known working revision: not established. ## Evidence and prior checks The affected [source case](https://git.erikinkinen.fi/erix/integration/src/commit/bd983dc4e479400734b1d168bf060c90e30e3c92/tests/owned_command_caller_clock_test.py) uses the same timeout helper as the fractional TERM, minute-suffixed HUP and disabled-clock cases. Their coverage must remain intact. ## Tracking - [ ] Establish readiness through genuine child custody before measuring the blocked-write cancellation interval. - [ ] Preserve asynchronous interruption, exact signal status and native cleanup assertions. - [ ] Keep the existing interval and enclosing limits; do not replace the test with immediate self-signalling or a longer timeout. - [ ] Demonstrate the corrected case in CI.
erikinkinen added this to the Alpha 1 milestone 2026-11-06 22:42:45 +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#477
No description provided.