generated from erix/meta
[BUG] Independent terminal CI probe fails in serial input #48
Labels
No labels
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/integration#48
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The independent terminal feature-image probe fails in CI 1600 after all 486 catalog scenarios, earlier image/input gates and the fbcon, serial and none terminal modes pass. The composed VM-command status is 125 and the serial input status is 1; the failing operation and cause remain unknown.
Reproduction
Observed in retained original CI; no new VM rerun or failure-frequency estimate.
These commands select the final mode of the original four-mode workflow loop after its normal source/build preparation. The wrapper uses COM1 with native-console-mode and CONSOLE_MODE=independent.
Expected and actual behavior
Expected behavior is completion of the independent terminal probe. Actual receipt:
stage=serial-input runner_exit=1 vm_exit=125 expected_vm_exit=0 physical_input_exit=unknown serial_input_exit=1 physical_cleanup_requested=0. Status 125 is the composed VM-command result; a raw QEMU exit or timeout cause cannot be inferred from it.Environment and identity
5a593a5b308aa781bc796cd145ba7a49a4a559d9.The workflow selects its original pinned component graph and x86_64 QEMU/OVMF images. Complete CI logs and original wrappers were inspected. Image/firmware artifact bytes and inner runner receipts were not downloaded; their exact digests and the guest cause remain unverified. Existing 120-second total, 15-second serial-progress and 10-second input-command limits remain unchanged.
Evidence and prior checks
The independent probe starts at 11:36:58 UTC and reports failure at 11:38:56 UTC on September 13. All four feature disk images were built, and the first three mode probes passed. Image construction alone does not establish the failed independent mode behavior.
Rust and Markdown jobs pass. Complete logs are retained with no compiler/lint warning candidates. No unchanged retry, cancellation, dispatch or threshold adjustment was performed for this report.
Tracking
Retain independent terminal routing and full input assertions. Diagnose the failed serial milestone, preserve actual child and cleanup statuses, and add a focused regression when the cause is established.
erikinkinen referenced this issue2026-09-14 07:36:11 +02:00
erikinkinen referenced this issue from erix/docs2026-09-14 07:57:37 +02:00