[BUG] Physical utility host fixture expires while settling input at a consent prompt #74

Open
opened 2026-09-23 07:30:16 +02:00 by erikinkinen · 0 comments
Owner

Summary

The positive physical utility host fixture fails in Integration CI 1731 before the catalog VM suite runs. Its real input observer reaches the third copy-consent review, then refuses further input because the original settling interval no longer fits its deadline. This is a host fake-socket fixture failure, not an observed EriX guest failure.

Reproduction

The original workflow at 1d7f8d9136b6f14a97e41604f5fa5d8a2b0663d4 invokes the maintained helper tests. The failing test is UtilityFixtureTests.test_actual_physical_dispatch_complete_sequence_and_separate_consents in native_utility_fixture_test.py. It runs the real disk runner and physical observer against an explicitly selected fake QEMU process, fake guest sockets and nonbootable fixture files. No new reproduction or unchanged retry was performed; frequency and a deterministic smaller trigger remain unknown.

Expected and actual behavior

The complete positive command sequence should satisfy its existing status, output, separate-consent and input-order assertions within unchanged limits. Instead the test expects runner exit 0 and receives 1. The observer reports timed out while settling physical input. The last retained event is trusted_prompt_ready for command 9, review 3, the write-contents request for /bin/cp and selector nativewriteblocked, at elapsed 14.267924 seconds. This locates the refusal without establishing host contention, a socket race or a defective timeout as its cause.

The suite finishes with one failure among five tests after 36.461 seconds. The remaining catalog and image gates are not reached by this run.

Environment and identity

Integration source is 1d7f8d9136b6f14a97e41604f5fa5d8a2b0663d4, push run 1731/API10311, main job 22124, attempt 1. The test selects the physical native-utility route with a 3-second per-command limit, 60-second hard limit, 15-second stall limit and 65-second outer subprocess limit. Its fake guest uses explicit fixture font and source files; no real bootable image or Kernel execution is involved. No deadline or consent requirement was changed. A last-known-good environment/source pair for this failure is not established.

Evidence and prior checks

Complete original CI review — 28 September 2026:

These are additional original observations. No unchanged job was rerun, and an identical underlying cause to earlier observations is not assumed.

  • CI1815, 125bcbb5fe1145f7e085ffe4d2bfea5eeca23616: The positive physical utility host fixture expires before its remaining consent-observation interval fits. The catalog VM suite is not reached. Three complete logs contain 320,496 bytes and zero warning candidates. Rust and Markdown pass. Last event: choice_injected, command 9, review 3, elapsed 14.370557 seconds.
  • CI1823, 4246853dfab3cb434f24ca1a169d5be60cf402c9: The positive physical utility host fixture expires before its remaining consent-observation interval fits. The catalog VM suite is not reached. Three complete logs contain 338,621 bytes and zero warning candidates. Rust and Markdown pass. Last event: choice_injected, command 11, review 3, elapsed 19.215402 seconds.

Three complete original CI logs total 318,438 bytes and have zero warning candidates. Rust and Markdown jobs pass. The retained main log includes the assertion, observer events and complete failure output. Source review confirms that the input-settling helper rejects when the remaining deadline cannot hold its existing drain interval. This is not proof that increasing that deadline is appropriate.

Other original runs pass this host fixture and proceed into VM tests; CI 1734 passes its entire workflow at a different source revision. Neither observation closes this failure or supplies a controlled performance comparison.

Tracking

Track source-bound diagnosis and unchanged-limit correction through Integration PR #12 and Phase 6 completion. Keep this host fixture distinct from release physical utility guest failures. Preserve the original failed run; profile the observer and fixture before choosing a correction.

Original interactive and helper CI failures — 24 September 2026: Push run 1755, Integration 5057a4134cbf0461f5587b9fe9278121febae8de, fails the same positive physical utility fixture before catalog VM execution. Its refusal is insufficient original utility deadline for consent observation; the final observer event is choice_injected for command 4, review 3 at 5.922009 seconds. The preceding review is the write-contents request for /bin/cp and nativeemptycopy. This differs from the original command 9 settling refusal; shared fixture ownership does not establish an identical cause.

All three original terminal logs are retained, totaling 285,839 bytes, with verified hashes and lengths and zero warning candidates. Rust and Markdown pass. The fake-socket fixture's existing 3-second command, 60-second hard and 15-second stall limits remain unchanged. No guest runs in this fixture, no failed input was retried, and this report remains open pending an attributed unchanged-limit correction.

Additional original CI classification — 24 September 2026:

  • Run 1767, b40f1742cfde6658a08774c0c869399b8dbb3df0, integration job 22364: The positive physical utility host fixture times out after choice_waited_for_enter for command 9, review 3. Catalog VMs are not reached. Report #74. Three complete logs: 320,159 bytes.

Original complete logs and relevant workflow/runner Git blobs verify. Rust and Markdown pass, with zero warning candidates. These observations do not establish an identical cause to the earlier report, an attributed correction or a Kernel regression. All original failures and requirements are retained without retry; this report remains open pending correction evidence.

Additional original host-fixture evidence — 24 September 2026: Integration run 1780, source 46ae17e84abdc1e72e89fd7c50c766c54f3bcc03, again fails UtilityFixtureTests.test_actual_physical_dispatch_complete_sequence_and_separate_consents before catalog VM execution. The observer reports timed out while settling physical input after choice_waited_for_enter for command 4, review 3 at 7.129914 seconds, for the write-contents consent on /bin/cp and nativeemptycopy. The suite reports one failure among five tests after 29.589 seconds. This remains a fake-socket host fixture, not guest execution.

Three complete original logs total 287,323 bytes, with verified hashes/lengths and zero warning candidates. Rust and Markdown pass. The original 3-second command, 60-second hard, 15-second stall and 65-second outer subprocess limits remain unchanged. This confirms another retained failure of the same fixture; an identical underlying cause is not established. No rerun or workaround was used, and the report remains open.

## Summary The positive physical utility host fixture fails in [Integration CI 1731](https://git.erikinkinen.fi/erix/integration/actions/runs/1731) before the catalog VM suite runs. Its real input observer reaches the third copy-consent review, then refuses further input because the original settling interval no longer fits its deadline. This is a host fake-socket fixture failure, not an observed EriX guest failure. ## Reproduction The original workflow at `1d7f8d9136b6f14a97e41604f5fa5d8a2b0663d4` invokes the maintained helper tests. The failing test is `UtilityFixtureTests.test_actual_physical_dispatch_complete_sequence_and_separate_consents` in [native_utility_fixture_test.py](https://git.erikinkinen.fi/erix/integration/src/commit/1d7f8d9136b6f14a97e41604f5fa5d8a2b0663d4/tests/native_utility_fixture_test.py). It runs the real disk runner and physical observer against an explicitly selected fake QEMU process, fake guest sockets and nonbootable fixture files. No new reproduction or unchanged retry was performed; frequency and a deterministic smaller trigger remain unknown. ## Expected and actual behavior The complete positive command sequence should satisfy its existing status, output, separate-consent and input-order assertions within unchanged limits. Instead the test expects runner exit 0 and receives 1. The observer reports `timed out while settling physical input`. The last retained event is `trusted_prompt_ready` for command 9, review 3, the write-contents request for `/bin/cp` and selector `nativewriteblocked`, at elapsed 14.267924 seconds. This locates the refusal without establishing host contention, a socket race or a defective timeout as its cause. The suite finishes with one failure among five tests after 36.461 seconds. The remaining catalog and image gates are not reached by this run. ## Environment and identity Integration source is `1d7f8d9136b6f14a97e41604f5fa5d8a2b0663d4`, push run 1731/API10311, main job 22124, attempt 1. The test selects the physical native-utility route with a 3-second per-command limit, 60-second hard limit, 15-second stall limit and 65-second outer subprocess limit. Its fake guest uses explicit fixture font and source files; no real bootable image or Kernel execution is involved. No deadline or consent requirement was changed. A last-known-good environment/source pair for this failure is not established. ## Evidence and prior checks Complete original CI review — 28 September 2026: These are additional original observations. No unchanged job was rerun, and an identical underlying cause to earlier observations is not assumed. - [CI1815](https://git.erikinkinen.fi/erix/integration/actions/runs/1815), `125bcbb5fe1145f7e085ffe4d2bfea5eeca23616`: The positive physical utility host fixture expires before its remaining consent-observation interval fits. The catalog VM suite is not reached. Three complete logs contain 320,496 bytes and zero warning candidates. Rust and Markdown pass. Last event: choice_injected, command 9, review 3, elapsed 14.370557 seconds. - [CI1823](https://git.erikinkinen.fi/erix/integration/actions/runs/1823), `4246853dfab3cb434f24ca1a169d5be60cf402c9`: The positive physical utility host fixture expires before its remaining consent-observation interval fits. The catalog VM suite is not reached. Three complete logs contain 338,621 bytes and zero warning candidates. Rust and Markdown pass. Last event: choice_injected, command 11, review 3, elapsed 19.215402 seconds. Three complete original CI logs total 318,438 bytes and have zero warning candidates. Rust and Markdown jobs pass. The retained main log includes the assertion, observer events and complete failure output. Source review confirms that the input-settling helper rejects when the remaining deadline cannot hold its existing drain interval. This is not proof that increasing that deadline is appropriate. Other original runs pass this host fixture and proceed into VM tests; [CI 1734](https://git.erikinkinen.fi/erix/integration/actions/runs/1734) passes its entire workflow at a different source revision. Neither observation closes this failure or supplies a controlled performance comparison. ## Tracking Track source-bound diagnosis and unchanged-limit correction through [Integration PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Keep this host fixture distinct from [release physical utility guest failures](https://git.erikinkinen.fi/erix/integration/issues/38). Preserve the original failed run; profile the observer and fixture before choosing a correction. Original interactive and helper CI failures — 24 September 2026: [Push run 1755](https://git.erikinkinen.fi/erix/integration/actions/runs/1755), Integration `5057a4134cbf0461f5587b9fe9278121febae8de`, fails the same positive physical utility fixture before catalog VM execution. Its refusal is `insufficient original utility deadline for consent observation`; the final observer event is `choice_injected` for command 4, review 3 at 5.922009 seconds. The preceding review is the write-contents request for `/bin/cp` and `nativeemptycopy`. This differs from the original command 9 settling refusal; shared fixture ownership does not establish an identical cause. All three original terminal logs are retained, totaling 285,839 bytes, with verified hashes and lengths and zero warning candidates. Rust and Markdown pass. The fake-socket fixture's existing 3-second command, 60-second hard and 15-second stall limits remain unchanged. No guest runs in this fixture, no failed input was retried, and this report remains open pending an attributed unchanged-limit correction. Additional original CI classification — 24 September 2026: - [Run 1767](https://git.erikinkinen.fi/erix/integration/actions/runs/1767), `b40f1742cfde6658a08774c0c869399b8dbb3df0`, integration job 22364: The positive physical utility host fixture times out after choice_waited_for_enter for command 9, review 3. Catalog VMs are not reached. [Report #74](https://git.erikinkinen.fi/erix/integration/issues/74). Three complete logs: 320,159 bytes. Original complete logs and relevant workflow/runner Git blobs verify. Rust and Markdown pass, with zero warning candidates. These observations do not establish an identical cause to the earlier report, an attributed correction or a Kernel regression. All original failures and requirements are retained without retry; this report remains open pending correction evidence. Additional original host-fixture evidence — 24 September 2026: [Integration run 1780](https://git.erikinkinen.fi/erix/integration/actions/runs/1780), source `46ae17e84abdc1e72e89fd7c50c766c54f3bcc03`, again fails `UtilityFixtureTests.test_actual_physical_dispatch_complete_sequence_and_separate_consents` before catalog VM execution. The observer reports `timed out while settling physical input` after `choice_waited_for_enter` for command 4, review 3 at 7.129914 seconds, for the write-contents consent on `/bin/cp` and `nativeemptycopy`. The suite reports one failure among five tests after 29.589 seconds. This remains a fake-socket host fixture, not guest execution. Three complete original logs total 287,323 bytes, with verified hashes/lengths and zero warning candidates. Rust and Markdown pass. The original 3-second command, 60-second hard, 15-second stall and 65-second outer subprocess limits remain unchanged. This confirms another retained failure of the same fixture; an identical underlying cause is not established. No rerun or workaround was used, and the report remains open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:22 +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#74
No description provided.