[BUG] Positive console-progress host fixture expires before completion #25

Closed
opened 2026-09-12 15:05:04 +02:00 by erikinkinen · 1 comment
Owner

Summary

The positive framebuffer-progress host fixture intermittently expired while its Python child was intended to emit verified console milestones. The watchdog returned 125 instead of zero before the VM catalog.

Reproduction

At b518b6ad1d2f3e7a36a5d796eaff3103c051bb84, run python3 tests/console_progress_watchdog_test.py. CI 1567 fails test_verified_completions_allow_framebuffer_work_without_serial_output; CI 1574 records another failure after diagnostic capture was added.

Expected and actual behavior

The complete ordered framebuffer transcript should preserve child status zero without serial output. The original 15-case group reports one failure, with no serial change for 250 ms. The precise failing event timeline was not retained, so its scheduling cause remains unknown.

The correction drives the actual watchdog and reader with a finite clock/child schedule and real files. Late evidence still cannot revive an expired deadline; activity alone supplies no milestone credit.

Environment and identity

  • Linux x86-64 host fixture; no QEMU or guest image.
  • Original bounds: 250 ms stall, 20 ms polling and 100 ms termination grace.
  • Correction: 96f1c21848d534683fc077779dd92d332e3e4779.
  • The production watchdog and existing real negative subprocess cases are unchanged by this correction.

Evidence and prior checks

CI 1575 and CI 1576 pass the corrected 21-case group. CI 2870, source 6f20e691142054bfae65eaf52d0fa5c3788879f8, independently passes all 21 in 2.738 seconds. Its complete module output is retained; the test bytes match the correction and current source.

Coverage includes complete milestones, before/exact/late expiry, malformed or stale evidence, serial-only activity and nonzero child status. The original failed runs remain distinct from these accepted host results.

Tracking

  • Remove real scheduling from positive policy assertions while exercising the actual reader and loop.
  • Preserve milestone, expiry, refusal and child-status controls.
  • Pass the corrected host module in matching original CI.

Implementation: PR #12. The separate serial fixture is #53. Broader process-lifetime and guest acceptance remain separate work.

## Summary The positive framebuffer-progress host fixture intermittently expired while its Python child was intended to emit verified console milestones. The watchdog returned 125 instead of zero before the VM catalog. ## Reproduction At `b518b6ad1d2f3e7a36a5d796eaff3103c051bb84`, run `python3 tests/console_progress_watchdog_test.py`. [CI 1567](https://git.erikinkinen.fi/erix/integration/actions/runs/1567) fails `test_verified_completions_allow_framebuffer_work_without_serial_output`; [CI 1574](https://git.erikinkinen.fi/erix/integration/actions/runs/1574) records another failure after diagnostic capture was added. ## Expected and actual behavior The complete ordered framebuffer transcript should preserve child status zero without serial output. The original 15-case group reports one failure, with no serial change for 250 ms. The precise failing event timeline was not retained, so its scheduling cause remains unknown. The correction drives the actual watchdog and reader with a finite clock/child schedule and real files. Late evidence still cannot revive an expired deadline; activity alone supplies no milestone credit. ## Environment and identity - Linux x86-64 host fixture; no QEMU or guest image. - Original bounds: 250 ms stall, 20 ms polling and 100 ms termination grace. - Correction: `96f1c21848d534683fc077779dd92d332e3e4779`. - The production watchdog and existing real negative subprocess cases are unchanged by this correction. ## Evidence and prior checks [CI 1575](https://git.erikinkinen.fi/erix/integration/actions/runs/1575) and [CI 1576](https://git.erikinkinen.fi/erix/integration/actions/runs/1576) pass the corrected 21-case group. [CI 2870](https://git.erikinkinen.fi/erix/integration/actions/runs/2870), source `6f20e691142054bfae65eaf52d0fa5c3788879f8`, independently passes all 21 in 2.738 seconds. Its complete module output is retained; the test bytes match the correction and current source. Coverage includes complete milestones, before/exact/late expiry, malformed or stale evidence, serial-only activity and nonzero child status. The original failed runs remain distinct from these accepted host results. ## Tracking - [x] Remove real scheduling from positive policy assertions while exercising the actual reader and loop. - [x] Preserve milestone, expiry, refusal and child-status controls. - [x] Pass the corrected host module in matching original CI. Implementation: [PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12). The separate serial fixture is [#53](https://git.erikinkinen.fi/erix/integration/issues/53). Broader process-lifetime and guest acceptance remain separate work.
Author
Owner

Closed after the original CI 2870 passes all 21 console-progress host tests. The tested fixture is byte-identical to its original correction and the current source. Production watchdog limits are unchanged.

Closed after the original [CI 2870](https://git.erikinkinen.fi/erix/integration/actions/runs/2870) passes all 21 console-progress host tests. The tested fixture is byte-identical to its original correction and the current source. Production watchdog limits are unchanged.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:10 +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#25
No description provided.