[BUG] Release COM1 command-line CI probe fails after its completion event #80

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

Summary

The release-image COM1 three-line probe fails after the development physical/serial probes and release physical probe pass. 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 serial 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 COM1 probe should complete all three distinct shell lines, retain their output assertions, and finish the owned VM shutdown without an injector error.

The receipt reports serial-input, runner 1, composed VM-command 0 and serial injector 1. The input diagnostic reports last_event=interactive_complete command=3. That observer event does not establish successful shutdown or identify the later failure. The subsequent interrupt and other input gates are not reached.

Environment and identity

  • Original run 1763, Integration 464819e47b042d2603a53e361e9938baa629d349, API run 10401, integration job 22336, 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 1763: three complete terminal logs, 13,384,454 bytes; main log SHA-256 b479c92077c0e5846c988a8e71a260bef5b9d3ef04b4371958b0d0766861d8c2. 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 COM1 three-line probe fails after the development physical/serial probes and release physical probe pass. 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 serial 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 COM1 probe should complete all three distinct shell lines, retain their output assertions, and finish the owned VM shutdown without an injector error. The receipt reports serial-input, runner 1, composed VM-command 0 and serial injector 1. The input diagnostic reports `last_event=interactive_complete command=3`. That observer event does not establish successful shutdown or identify the later failure. The subsequent interrupt and other input gates are not reached. ## Environment and identity - [Original run 1763](https://git.erikinkinen.fi/erix/integration/actions/runs/1763), Integration `464819e47b042d2603a53e361e9938baa629d349`, API run 10401, integration job 22336, 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 1763: three complete terminal logs, 13,384,454 bytes; main log SHA-256 `b479c92077c0e5846c988a8e71a260bef5b9d3ef04b4371958b0d0766861d8c2`. 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#80
No description provided.