[BUG] Release physical trusted-consent CI probe fails with vm-stall receipt #78

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

Summary

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

Reproduction

At Integration 5057a4134cbf0461f5587b9fe9278121febae8de, original CI run 1756 builds its pinned graph and canonical images, then invokes:

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

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=vm-stall, runner exit 1, composed VM-command exit 125 against expected 0, unknown physical and serial input statuses, and requested physical cleanup. This identifies the watchdog route, not a guest instruction, failed key, missing consent or root cause. Both serial consent probes and all directory, editor, utility and later input gates are not reached.

Environment and identity

  • Integration 5057a4134cbf0461f5587b9fe9278121febae8de, CI run 1756/API10382, integration job 22291, attempt 1.
  • Canonical release image, native x86-64 QEMU/OVMF, one virtual CPU, physical input, powerbox-prompt 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

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.

  • CI1816, 125bcbb5fe1145f7e085ffe4d2bfea5eeca23616: Release physical trusted-consent input exits 1 after its development counterpart passes. Three complete logs contain 13,459,213 bytes and zero warning candidates. Rust and Markdown pass.

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,385,466 bytes; their lengths and SHA-256 hashes verify with zero warning candidates. Main log SHA-256: 5046b19e8a3fa2ec76db520d4b5946a539f2ca5d25bce3d8d22a887da23ed062.

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.

## Summary The release physical trusted-review and Enter-consent probe fails after the development physical consent probe passes. This is an original CI observation; the underlying cause and first affected revision remain unknown. ## Reproduction At Integration `5057a4134cbf0461f5587b9fe9278121febae8de`, [original CI run 1756](https://git.erikinkinen.fi/erix/integration/actions/runs/1756) builds its pinned graph and canonical images, then invokes: ```sh ./tests/powerbox-prompt-vm.sh out/appliance/erix-release.img ``` The exact [workflow](https://git.erikinkinen.fi/erix/integration/src/commit/5057a4134cbf0461f5587b9fe9278121febae8de/.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=vm-stall`, runner exit 1, composed VM-command exit 125 against expected 0, unknown physical and serial input statuses, and requested physical cleanup. This identifies the watchdog route, not a guest instruction, failed key, missing consent or root cause. Both serial consent probes and all directory, editor, utility and later input gates are not reached. ## Environment and identity - Integration `5057a4134cbf0461f5587b9fe9278121febae8de`, CI run 1756/API10382, integration job 22291, attempt 1. - Canonical release image, native x86-64 QEMU/OVMF, one virtual CPU, physical input, `powerbox-prompt` 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 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. - [CI1816](https://git.erikinkinen.fi/erix/integration/actions/runs/1816), `125bcbb5fe1145f7e085ffe4d2bfea5eeca23616`: Release physical trusted-consent input exits 1 after its development counterpart passes. Three complete logs contain 13,459,213 bytes and zero warning candidates. Rust and Markdown pass. 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,385,466 bytes; their lengths and SHA-256 hashes verify with zero warning candidates. Main log SHA-256: `5046b19e8a3fa2ec76db520d4b5946a539f2ca5d25bce3d8d22a887da23ed062`. 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.
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#78
No description provided.