[BUG] Development serial trusted-consent CI probe fails after physical consent passes #85

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

Summary

The development COM1 trusted-review and consent probe fails after all 490 catalog VM scenarios and both physical consent probes pass. The original CI receipt identifies serial input as the failed stage; the underlying cause and first affected revision remain unknown.

Reproduction

Original Integration run 1777 at 4149f332dce6567f8f2db0f503154d8980a52e48 builds its pinned source graph and canonical images, then invokes:

./tests/powerbox-prompt-vm.sh out/appliance/erix-dev.img serial

The selected workflow establishes the input ordering. No new VM reproduction or unchanged-input retry was performed. Frequency, a deterministic smaller trigger and a last known good source/environment pair are unestablished.

Expected and actual behavior

The probe should complete the maintained command, trusted review, separate consent and cleanup assertions within the original deadlines and return success.

The receipt reports stage=serial-input, runner exit 1, composed VM-command exit 0, serial input exit 1, unknown physical-input status and no requested physical cleanup. The complete job log does not expose the failed command or injector diagnostic. This does not establish a guest crash, unauthorized consent or a shared cause with other input failures. Later release COM1 consent and directory/editor/utility gates are not reached.

Environment and identity

  • Integration 4149f332dce6567f8f2db0f503154d8980a52e48, run 1777/API10449, integration job 22446, attempt 1.
  • Canonical development image; native x86-64 QEMU/OVMF; serial input through the maintained trusted-consent wrapper.
  • Original workflow and wrapper source blobs were checked. No deadline, output condition or authority requirement was changed.
  • Raw guest, QMP and image artifacts have not been recovered; the composed VM-command receipt is not an independently recovered raw QEMU exit.

Evidence and prior checks

All 490 catalog VMs pass, as do the development and release canonical boot gates, earlier physical/serial command-line probes, physical interrupt/reuse probes and both physical consent probes. Rust and Markdown jobs pass. Three complete terminal job logs total 13,394,061 bytes with verified hashes and zero warning candidates. Main log SHA-256: 4788c908139c7d8b11b4c3865c95279702692a9f275ef95a2f0c3f4846d8ceb3.

The original failure remains retained without retry. Release serial consent report covers a different image profile; similarity of the failing stage does not establish an identical cause.

Tracking

Track diagnosis through Integration PR 12, integration validation and Phase 6 completion. Keep this report open until an attributed correction passes the unchanged contract. This observation does not itself attribute a Kernel regression.

## Summary The development COM1 trusted-review and consent probe fails after all 490 catalog VM scenarios and both physical consent probes pass. The original CI receipt identifies serial input as the failed stage; the underlying cause and first affected revision remain unknown. ## Reproduction [Original Integration run 1777](https://git.erikinkinen.fi/erix/integration/actions/runs/1777) at `4149f332dce6567f8f2db0f503154d8980a52e48` builds its pinned source graph and canonical images, then invokes: ```sh ./tests/powerbox-prompt-vm.sh out/appliance/erix-dev.img serial ``` The [selected workflow](https://git.erikinkinen.fi/erix/integration/src/commit/4149f332dce6567f8f2db0f503154d8980a52e48/.github/workflows/ci.yml) establishes the input ordering. No new VM reproduction or unchanged-input retry was performed. Frequency, a deterministic smaller trigger and a last known good source/environment pair are unestablished. ## Expected and actual behavior The probe should complete the maintained command, trusted review, separate consent and cleanup assertions within the original deadlines and return success. The receipt reports `stage=serial-input`, runner exit 1, composed VM-command exit 0, serial input exit 1, unknown physical-input status and no requested physical cleanup. The complete job log does not expose the failed command or injector diagnostic. This does not establish a guest crash, unauthorized consent or a shared cause with other input failures. Later release COM1 consent and directory/editor/utility gates are not reached. ## Environment and identity - Integration `4149f332dce6567f8f2db0f503154d8980a52e48`, run 1777/API10449, integration job 22446, attempt 1. - Canonical development image; native x86-64 QEMU/OVMF; serial input through the maintained trusted-consent wrapper. - Original workflow and wrapper source blobs were checked. No deadline, output condition or authority requirement was changed. - Raw guest, QMP and image artifacts have not been recovered; the composed VM-command receipt is not an independently recovered raw QEMU exit. ## Evidence and prior checks All 490 catalog VMs pass, as do the development and release canonical boot gates, earlier physical/serial command-line probes, physical interrupt/reuse probes and both physical consent probes. Rust and Markdown jobs pass. Three complete terminal job logs total 13,394,061 bytes with verified hashes and zero warning candidates. Main log SHA-256: `4788c908139c7d8b11b4c3865c95279702692a9f275ef95a2f0c3f4846d8ceb3`. The original failure remains retained without retry. [Release serial consent report](https://git.erikinkinen.fi/erix/integration/issues/76) covers a different image profile; similarity of the failing stage does not establish an identical cause. ## Tracking Track diagnosis 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). Keep this report open until an attributed correction passes the unchanged contract. This observation does not itself attribute a Kernel regression.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:20 +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#85
No description provided.