[BUG] Release serial trusted-consent CI probe fails after earlier input checks pass #76

Open
opened 2026-09-24 01:31:45 +02:00 by erikinkinen · 0 comments
Owner

Summary

The release COM1 trusted-review and consent probe fails after both physical consent probes and the development serial consent probe pass. This is an original CI observation; the underlying cause and first affected revision remain unknown.

Reproduction

At Integration c6ff552487457929b693a324990d7cf04792af74, original CI run 1753 builds its pinned graph and canonical images, then invokes:

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

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

Expected and actual behavior

The selected probe should complete the maintained input, output and separate-consent assertions within the original deadlines, shut down through its bounded runner 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 original log does not expose the failed command, consent observation or injector error. This locates the failed route without identifying its cause. Directory, editor, utility and later input gates are not reached.

Environment and identity

  • Integration c6ff552487457929b693a324990d7cf04792af74, CI run 1753/API10375, integration job 22274, attempt 1.
  • Canonical release image, native x86-64 QEMU/OVMF, one virtual CPU, serial input, powerbox-prompt-serial profile.
  • Original wrapper limits: 120 seconds hard, 15 seconds stall and 10 seconds per command. No deadline or acceptance condition was altered.
  • Original workflow, wrapper and shared input-runner Git blobs were checked. Full image, private guest and QMP artifact bytes were not downloaded; log status is not an independently recovered raw QEMU exit.

Evidence and prior checks

All 489 catalog VM scenarios and both canonical image boot gates pass before this failure. Rust 320/321-test configurations and Markdown pass. Three complete original terminal job logs total 13,387,014 bytes; their lengths and SHA-256 hashes verify with zero warning candidates. Main log SHA-256: cebaa9118bbacffbb6aebd9beb814a24be02818bd2aeeb818cf7f3f9c88c406b.

The success of earlier probes does not repair this failure or establish a common cause with other input reports. Source-bound diagnosis must retain the original consent, cleanup, timing and authority requirements. The original run remains retained without retry.

Tracking

Track diagnosis and correction through Integration PR 12, integration validation and Phase 6 completion. Keep this report open until an attributed correction passes the unchanged contract. The reported failure alone does not demonstrate a Kernel regression or unauthorized consent.

Additional original CI classification — 24 September 2026:

  • Run 1757, 98c9756421d2405c5a5132916ce80d1b9396d2a2, integration job 22298: Release serial trusted-consent input fails after earlier consent probes pass. Report #76. Three complete logs: 13,388,033 bytes. Receipt: stage=serial-input runner_exit=1 vm_exit=0 expected_vm_exit=0 physical_input_exit=unknown serial_input_exit=1 physical_cleanup_requested=0.

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.

## Summary The release COM1 trusted-review and consent probe fails after both physical consent probes and the development serial consent probe pass. This is an original CI observation; the underlying cause and first affected revision remain unknown. ## Reproduction At Integration `c6ff552487457929b693a324990d7cf04792af74`, [original CI run 1753](https://git.erikinkinen.fi/erix/integration/actions/runs/1753) builds its pinned graph and canonical images, then invokes: ```sh ./tests/powerbox-prompt-vm.sh out/appliance/erix-release.img serial ``` The exact [workflow](https://git.erikinkinen.fi/erix/integration/src/commit/c6ff552487457929b693a324990d7cf04792af74/.github/workflows/ci.yml) establishes the image and input ordering. No new VM reproduction or unchanged-input retry was performed. Frequency, a deterministic smaller trigger and a last known good environment/source pair are unestablished. ## Expected and actual behavior The selected probe should complete the maintained input, output and separate-consent assertions within the original deadlines, shut down through its bounded runner 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 original log does not expose the failed command, consent observation or injector error. This locates the failed route without identifying its cause. Directory, editor, utility and later input gates are not reached. ## Environment and identity - Integration `c6ff552487457929b693a324990d7cf04792af74`, CI run 1753/API10375, integration job 22274, attempt 1. - Canonical release image, native x86-64 QEMU/OVMF, one virtual CPU, serial input, `powerbox-prompt-serial` profile. - Original wrapper limits: 120 seconds hard, 15 seconds stall and 10 seconds per command. No deadline or acceptance condition was altered. - Original workflow, wrapper and shared input-runner Git blobs were checked. Full image, private guest and QMP artifact bytes were not downloaded; log status is not an independently recovered raw QEMU exit. ## Evidence and prior checks All 489 catalog VM scenarios and both canonical image boot gates pass before this failure. Rust 320/321-test configurations and Markdown pass. Three complete original terminal job logs total 13,387,014 bytes; their lengths and SHA-256 hashes verify with zero warning candidates. Main log SHA-256: `cebaa9118bbacffbb6aebd9beb814a24be02818bd2aeeb818cf7f3f9c88c406b`. The success of earlier probes does not repair this failure or establish a common cause with other input reports. Source-bound diagnosis must retain the original consent, cleanup, timing and authority requirements. The original run remains retained without retry. ## 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). Keep this report open until an attributed correction passes the unchanged contract. The reported failure alone does not demonstrate a Kernel regression or unauthorized consent. Additional original CI classification — 24 September 2026: - [Run 1757](https://git.erikinkinen.fi/erix/integration/actions/runs/1757), `98c9756421d2405c5a5132916ce80d1b9396d2a2`, integration job 22298: Release serial trusted-consent input fails after earlier consent probes pass. [Report #76](https://git.erikinkinen.fi/erix/integration/issues/76). Three complete logs: 13,388,033 bytes. Receipt: `stage=serial-input runner_exit=1 vm_exit=0 expected_vm_exit=0 physical_input_exit=unknown serial_input_exit=1 physical_cleanup_requested=0`. 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.
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#76
No description provided.