[BUG] Final image quiet-time test assumes fast capture #18

Closed
opened 2026-10-15 03:29:25 +02:00 by erikinkinen · 1 comment
Owner

Summary

The final image quiet-time test can expire during capture, before reaching the check it intends to exercise.

Reproduction

Run 514, Rust job, attempt 1 fails at Exsh ffe9473ca542e332ab49a5073bf387dd54e361c0 in test_final_original_quiet_check_runs_after_guard_binding_before_child_creation.

Expected and actual behavior

The test should finish image binding, expire the quiet interval at the final check, and verify that no child starts. It starts a 50 ms interval before streaming and hashing the image, then sleeps 80 ms after binding. Capture checks that same interval, so slow capture can select an earlier timeout. CI fails the bound and closed assertion; the exact timeout location is unrecorded.

Environment and identity

Linux x86-64, feature/posix-compat, push workflow ci.yml. This is a host fixture; no guest image is involved.

Evidence and prior checks

The complete original log reports one error among 744 Python tests. Four native builds finish before the failure. This does not establish unsafe child creation or a new frame-gate result.

Tracking

8540bcf4 changes only the fixture's component clock and adds a non-expired companion. Production deadlines and real capture-expiry coverage are unchanged. The corrected source passes all 745 local controls. The separate frame-proof work remains in #4.

  • Select post-binding expiry independently of capture latency.
  • Preserve no-spawn, activity and retirement checks, with a non-expired companion.
  • Confirm the corrected control in current CI.
## Summary The final image quiet-time test can expire during capture, before reaching the check it intends to exercise. ## Reproduction [Run 514, Rust job, attempt 1](https://git.erikinkinen.fi/erix/exsh/actions/runs/514/jobs/0/attempt/1) fails at Exsh `ffe9473ca542e332ab49a5073bf387dd54e361c0` in `test_final_original_quiet_check_runs_after_guard_binding_before_child_creation`. ## Expected and actual behavior The test should finish image binding, expire the quiet interval at the final check, and verify that no child starts. It starts a 50 ms interval before streaming and hashing the image, then sleeps 80 ms after binding. Capture checks that same interval, so slow capture can select an earlier timeout. CI fails the `bound and closed` assertion; the exact timeout location is unrecorded. ## Environment and identity Linux x86-64, `feature/posix-compat`, push workflow `ci.yml`. This is a host fixture; no guest image is involved. ## Evidence and prior checks The complete original log reports one error among 744 Python tests. Four native builds finish before the failure. This does not establish unsafe child creation or a new frame-gate result. ## Tracking [8540bcf4](https://git.erikinkinen.fi/erix/exsh/commit/8540bcf44fbfd24a51d0e399077f25e4b6651988) changes only the fixture's component clock and adds a non-expired companion. Production deadlines and real capture-expiry coverage are unchanged. The corrected source passes all 745 local controls. The separate frame-proof work remains in [#4](https://git.erikinkinen.fi/erix/exsh/issues/4). - [x] Select post-binding expiry independently of capture latency. - [x] Preserve no-spawn, activity and retirement checks, with a non-expired companion. - [x] Confirm the corrected control in current CI.
Author
Owner

Run 516, Rust job, attempt 1 passes all 745 Python controls at 8540bcf4, including the corrected expiry fixture and its non-expired companion. The timing fix is complete. The job later refuses incomplete frame/source membership; that remains tracked in #4.

[Run 516, Rust job, attempt 1](https://git.erikinkinen.fi/erix/exsh/actions/runs/516/jobs/0/attempt/1) passes all 745 Python controls at `8540bcf4`, including the corrected expiry fixture and its non-expired companion. The timing fix is complete. The job later refuses incomplete frame/source membership; that remains tracked in [#4](https://git.erikinkinen.fi/erix/exsh/issues/4).
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:49 +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/exsh#18
No description provided.