[BUG] Final image quiet-time test assumes fast capture #18
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/exsh#18
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
ffe9473ca542e332ab49a5073bf387dd54e361c0intest_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 closedassertion; the exact timeout location is unrecorded.Environment and identity
Linux x86-64,
feature/posix-compat, push workflowci.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.
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.