[BUG] Development COM1 editor probe fails after the complete VM catalog passes #67

New issue

Open

opened 2026-09-19 18:46:38 +02:00 by erikinkinen · 0 comments

erikinkinen commented

2026-09-19 18:46:38 +02:00

Owner

Summary

Original Integration CI 1678 fails the development COM1 command-history/cursor probe after all 489 catalog VM scenarios pass. The immediately preceding development physical editor probe passes. The input-stage diagnostic does not identify the failed edit or transport operation; cause and frequency remain unclassified.

Reproduction

Observed once in the original pull-request workflow at Integration 78557a6c672ecf426dfe894a01cc4aeec73b5e3c. The exact workflow invokes ./tests/native-editor-vm.sh serial out/appliance/erix-dev.img after its development physical-input counterpart. Preserve the original scenario, input deadlines and source graph. No unchanged rerun or local reproduction is claimed.

Expected and actual behavior

Expected: the development COM1 editor probe completes its command-history and cursor checks, allowing later release editor and console gates to run.

Actual: at 16:24:42 UTC on 19 September 2026, the runner reports stage=serial-input, runner_exit=1, composed vm_exit=125, expected_vm_exit=0, serial_input_exit=1, physical_input_exit=unknown, and physical_cleanup_requested=0. The native input diagnostic reports last_event=unavailable. The workflow stops with exit 1. The composed VM status is not proof of QEMU's direct exit status or a guest fault.

Environment and identity

Integration revision: 78557a6c672ecf426dfe894a01cc4aeec73b5e3c.
Original workflow: CI 1678, pull-request event, development appliance image, x86_64 COM1 input.
Original job ID: 21353; its complete log is 13,280,046 bytes, SHA256 ac025683a12138b3107addc794466805fe2ffbb469912e37604665222a7167bb.
Exact input/image checks are selected by the committed workflow and original resolved component catalog; no replacement source or changed limit is used.
No known reliable passing revision for this specific observed failure is established.

Evidence and prior checks

All 489 catalog scenarios, both maintained native Kernel diagnostics and preceding image/input gates pass. Development physical editor passes before development serial editor fails. Rust and Markdown jobs pass independently. All three complete original logs total 13,384,697 bytes with zero warning candidates. Later release editor/console gates were not reached and must not be reported as passing. Raw inner input/VM evidence is referenced by the runner but is not present in the collected job logs; no root cause is inferred from the outer status alone.

Tracking

Keep this development COM1 observation distinct from release COM1 editor failure, release physical editor failure, and development COM1 directory failure. Different routes do not establish a shared cause. Obtain bounded original input progress and runner-owned evidence before changing behavior or limits.

## Summary Original Integration CI 1678 fails the development COM1 command-history/cursor probe after all 489 catalog VM scenarios pass. The immediately preceding development physical editor probe passes. The input-stage diagnostic does not identify the failed edit or transport operation; cause and frequency remain unclassified. ## Reproduction Observed once in the original pull-request workflow at Integration `78557a6c672ecf426dfe894a01cc4aeec73b5e3c`. The exact workflow invokes `./tests/native-editor-vm.sh serial out/appliance/erix-dev.img` after its development physical-input counterpart. Preserve the original scenario, input deadlines and source graph. No unchanged rerun or local reproduction is claimed. ## Expected and actual behavior Expected: the development COM1 editor probe completes its command-history and cursor checks, allowing later release editor and console gates to run. Actual: at 16:24:42 UTC on 19 September 2026, the runner reports `stage=serial-input`, `runner_exit=1`, composed `vm_exit=125`, `expected_vm_exit=0`, `serial_input_exit=1`, `physical_input_exit=unknown`, and `physical_cleanup_requested=0`. The native input diagnostic reports `last_event=unavailable`. The workflow stops with exit 1. The composed VM status is not proof of QEMU's direct exit status or a guest fault. ## Environment and identity - Integration revision: `78557a6c672ecf426dfe894a01cc4aeec73b5e3c`. - Original workflow: [CI 1678](https://git.erikinkinen.fi/erix/integration/actions/runs/1678), pull-request event, development appliance image, x86_64 COM1 input. - Original job ID: 21353; its complete log is 13,280,046 bytes, SHA256 `ac025683a12138b3107addc794466805fe2ffbb469912e37604665222a7167bb`. - Exact input/image checks are selected by the committed workflow and original resolved component catalog; no replacement source or changed limit is used. - No known reliable passing revision for this specific observed failure is established. ## Evidence and prior checks All 489 catalog scenarios, both maintained native Kernel diagnostics and preceding image/input gates pass. Development physical editor passes before development serial editor fails. Rust and Markdown jobs pass independently. All three complete original logs total 13,384,697 bytes with zero warning candidates. Later release editor/console gates were not reached and must not be reported as passing. Raw inner input/VM evidence is referenced by the runner but is not present in the collected job logs; no root cause is inferred from the outer status alone. ## Tracking Keep this development COM1 observation distinct from [release COM1 editor failure](https://git.erikinkinen.fi/erix/integration/issues/37), [release physical editor failure](https://git.erikinkinen.fi/erix/integration/issues/13), and [development COM1 directory failure](https://git.erikinkinen.fi/erix/integration/issues/56). Different routes do not establish a shared cause. Obtain bounded original input progress and runner-owned evidence before changing behavior or limits. Related: [WIP integration PR](https://git.erikinkinen.fi/erix/integration/pulls/12), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65).

erikinkinen added the

bug

phase-6

labels

2026-09-19 18:46:38 +02:00

erikinkinen referenced this issue from erix/kernel

2026-09-19 20:18:34 +02:00

[FEATURE] Bind staged child cleanup to its native supervisor lifetime #19

erikinkinen referenced this issue from erix/kernel

2026-09-19 20:18:35 +02:00

[FEATURE] Supply authorized memory, TLS, threads and race-free blocking for runtimes #1

erikinkinen referenced this issue from erix/kernel