[BUG] Release physical command-line CI probe fails at input and watchdog stages #81

Open
opened 2026-09-24 13:58:39 +02:00 by erikinkinen · 0 comments
Owner

Summary

The release-image physical three-line probe fails in three original CI runs after both development line probes pass. The observations have different failure stages; a common cause is unestablished. The cause and first affected revision remain unestablished.

Reproduction

The retained original workflow builds its pinned graph and invokes:

./tests/interactive-shell-lines-vm.sh physical out/appliance/erix-release.img

The workflow supplies the image and prerequisite setup. Original workflow and relevant fixture/runner Git blobs were checked against the retained revision. No new VM reproduction, unchanged-input retry, deterministic trigger or failure-frequency estimate is claimed.

Expected and actual behavior

The release physical-input probe should complete all three distinct shell lines and their output assertions, then finish bounded cleanup within the original limits.

Run 1764 reports physical-input, runner 1, composed VM-command 0 and physical injector 1; its last event is command_injected command=1, with phase=command-output cleanup=none. Runs 1765 and 1769 report vm-stall, runner 1, composed VM-command 125, unknown injector statuses, requested physical cleanup and last_event=unavailable. These are separate original observations, not retries. The release serial-line and later input gates are not reached. The development-image report #32 remains separate.

Environment and identity

  • Original run 1764, Integration 464819e47b042d2603a53e361e9938baa629d349, API run 10402, integration job 22339, attempt 1.
  • Original run 1765, Integration f7d1d2a7c7eb5f1d761ffec76623576e0d05a5d6, API run 10407, integration job 22350, attempt 1.
  • Original run 1769, Integration f67ec4fb039dde1944345e599ce1c3be2cac765f, API run 10419, integration job 22378, attempt 1.

Native x86-64 QEMU/OVMF and the workflow-selected image, input transport and console configuration. Original wrapper limits remain 120 seconds hard, 15 seconds stall and 10 seconds per command. Raw image, guest and QMP artifact bytes have not been recovered from CI; the receipt is not an independently observed raw QEMU exit.

Evidence and prior checks

All 489 catalog VM scenarios, both canonical image boot gates, Rust 320/321-test configurations and Markdown pass before the later input failure. Run 1764: three complete terminal logs, 13,384,492 bytes; main log SHA-256 04bd7f42f94d14d9437249154891751e7c5240b990c2be05512af8a238bbb4d0.
Run 1765: three complete terminal logs, 13,384,417 bytes; main log SHA-256 4516879d789defedc70a8ebd2a2dd73dd09d8bafaec8860804d7b33fa66fdf8e.
Run 1769: three complete terminal logs, 13,383,719 bytes; main log SHA-256 65230f64a0bb1f37a9c93c2c8675eea0bf3523645b317d11960338af1a525506. Complete retained log lengths and hashes verify, with zero warning candidates. Passing neighboring runs do not repair these failures. The failed-stage observations do not attribute a Kernel regression or establish an authority violation.

Tracking

Track diagnosis and correction through Integration PR 12, integration validation and Phase 6 completion. Preserve the original timing, output, consent and cleanup contracts. Keep this report open until an attributed correction passes the unchanged applicable requirements.

## Summary The release-image physical three-line probe fails in three original CI runs after both development line probes pass. The observations have different failure stages; a common cause is unestablished. The cause and first affected revision remain unestablished. ## Reproduction The retained original workflow builds its pinned graph and invokes: ```sh ./tests/interactive-shell-lines-vm.sh physical out/appliance/erix-release.img ``` The workflow supplies the image and prerequisite setup. Original workflow and relevant fixture/runner Git blobs were checked against the retained revision. No new VM reproduction, unchanged-input retry, deterministic trigger or failure-frequency estimate is claimed. ## Expected and actual behavior The release physical-input probe should complete all three distinct shell lines and their output assertions, then finish bounded cleanup within the original limits. Run 1764 reports physical-input, runner 1, composed VM-command 0 and physical injector 1; its last event is `command_injected command=1`, with `phase=command-output cleanup=none`. Runs 1765 and 1769 report vm-stall, runner 1, composed VM-command 125, unknown injector statuses, requested physical cleanup and `last_event=unavailable`. These are separate original observations, not retries. The release serial-line and later input gates are not reached. The development-image report #32 remains separate. ## Environment and identity - [Original run 1764](https://git.erikinkinen.fi/erix/integration/actions/runs/1764), Integration `464819e47b042d2603a53e361e9938baa629d349`, API run 10402, integration job 22339, attempt 1. - [Original run 1765](https://git.erikinkinen.fi/erix/integration/actions/runs/1765), Integration `f7d1d2a7c7eb5f1d761ffec76623576e0d05a5d6`, API run 10407, integration job 22350, attempt 1. - [Original run 1769](https://git.erikinkinen.fi/erix/integration/actions/runs/1769), Integration `f67ec4fb039dde1944345e599ce1c3be2cac765f`, API run 10419, integration job 22378, attempt 1. Native x86-64 QEMU/OVMF and the workflow-selected image, input transport and console configuration. Original wrapper limits remain 120 seconds hard, 15 seconds stall and 10 seconds per command. Raw image, guest and QMP artifact bytes have not been recovered from CI; the receipt is not an independently observed raw QEMU exit. ## Evidence and prior checks All 489 catalog VM scenarios, both canonical image boot gates, Rust 320/321-test configurations and Markdown pass before the later input failure. Run 1764: three complete terminal logs, 13,384,492 bytes; main log SHA-256 `04bd7f42f94d14d9437249154891751e7c5240b990c2be05512af8a238bbb4d0`. Run 1765: three complete terminal logs, 13,384,417 bytes; main log SHA-256 `4516879d789defedc70a8ebd2a2dd73dd09d8bafaec8860804d7b33fa66fdf8e`. Run 1769: three complete terminal logs, 13,383,719 bytes; main log SHA-256 `65230f64a0bb1f37a9c93c2c8675eea0bf3523645b317d11960338af1a525506`. Complete retained log lengths and hashes verify, with zero warning candidates. Passing neighboring runs do not repair these failures. The failed-stage observations do not attribute a Kernel regression or establish an authority violation. ## Tracking Track diagnosis and correction through [Integration PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12), [integration validation](https://git.erikinkinen.fi/erix/integration/issues/3) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Preserve the original timing, output, consent and cleanup contracts. Keep this report open until an attributed correction passes the unchanged applicable requirements.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:21 +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#81
No description provided.