[BUG] Development COM1 directory CI probe fails after physical directory input passes #77

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

Summary

The development COM1 directory probe fails after all four consent probes and development physical directory input pass. This is an original CI observation; the underlying cause and first affected revision remain unknown.

Reproduction

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

./tests/native-directory-vm.sh serial out/appliance/erix-dev.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=serial-input, runner exit 1, composed VM-command exit 0, serial input exit 1, unknown physical input status and no requested physical cleanup. The retained input diagnostic is profile=native-directory transport=serial input_exit=1 last_event=command_injected command=4. Injection of command 4 is the last observed event, not proof of guest execution, a particular missing output or the cause. The release directory probes, editor, utility and later input gates are not reached.

Environment and identity

  • Integration c6ff552487457929b693a324990d7cf04792af74, CI run 1754/API10376, integration job 22277, attempt 1.
  • Canonical development image, native x86-64 QEMU/OVMF, one virtual CPU, serial input, native-directory 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,389,457 bytes; their lengths and SHA-256 hashes verify with zero warning candidates. Main log SHA-256: 695690664bed8768cf9b9c5a0eef035e8f22003f628e8988dc9d879dd4f5a8db.

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

Older original CI observation — 25 September 2026: run1782 at 96000d3e028173aad425f3b7029a92cca620a654 passes490/490 catalog scenarios, Rust and Markdown, then fails the development serial native-directory probe. The retained diagnostics report input_exit1 and unavailable last input event; composed vm_exit125 is not proof of a raw QEMU exit status. This matches the existing observation class without establishing its cause. No failed input was rerun.

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.

Original development COM1 directory CI observation — 24 September 2026: Run 1775, Integration 591d96f3ffb502c65621e8eea4400041d69f622d, API10437/job22420/attempt1, fails the development COM1 directory probe after all 489 catalog VMs, both canonical images, all four consent probes and development physical directory input pass. The receipt reports serial-input, runner 1, composed VM-command 0, serial input 1 and no requested physical cleanup. The last event is native_directory_complete at command 14. This differs from the earlier command-injected observation in bug report #77; a completion event does not establish successful final transport cleanup or a shared cause.

Three complete original terminal logs verify: 13,387,523 bytes, matching hashes and zero warning candidates. The main log SHA-256 is 28d124214a3ee9e916c6e47b35838fccdfaa06a33c61c84b03d9cad7f1e4000e. Rust 320/321 matrices and Markdown pass; source-bound workflow and runner blobs verify. Original 120/15/10 limits and all output/cleanup requirements remain unchanged. Raw guest/QMP artifacts are not recovered. No failed input was rerun, cause or Kernel regression attributed, or correction acceptance inferred. Report #77 remains open; master acceptance remains 15 of 460 items, weighted 3.48%.

Original development COM1 directory CI observation — run 1779, 24 September 2026.

Run 1779, Integration 46ae17e84abdc1e72e89fd7c50c766c54f3bcc03, API10455/job22460/attempt1, fails the development COM1 directory probe. The original workflow invokes ./tests/native-directory-vm.sh serial out/appliance/erix-dev.img after all 490 catalog VM scenarios, both canonical images, all four physical/serial consent probes and development physical directory input pass. Rust configurations with 320/321 tests, both five-test profiler ABI configurations, and Markdown also pass.

The receipt reports stage=serial-input, runner exit 1, composed VM-command exit 0, expected VM-command exit 0, serial input exit 1, unknown physical-input status and no requested physical cleanup. Its last recorded milestone is profile=native-directory transport=serial input_exit=1 last_event=command_injected command=5. In the exact selected input source, command 5 runs ls -la tmp and then a status-reporting command. The next maintained step waits for fresh enumeration consent for tmp; later steps request metadata for tmp and deny metadata for tmp/... No fresh-consent event for command 5 appears in the summary. This source order does not establish that the guest received the command, why the observation failed, or a common cause with the earlier command-4 or command-14 observations.

Three complete original terminal logs total 13,394,748 bytes with verified hashes and zero warning candidates. Main log SHA-256: 8474634f145ddaa8ded00cabd5950701e0fcf111ec956593b4e210c877c461e0. The 11 earlier error-shaped diagnostics belong to passing negative controls; the late serial probe is the actual job failure. Original limits remain 120 seconds hard, 15 seconds stall and 10 seconds per command, with one virtual CPU. No failed input was rerun, workflow cancelled, deadline or acceptance requirement changed. Raw guest/QMP/image artifacts have not been recovered, so the composed VM-command exit is not an independently recovered raw QEMU exit.

Keep this report open pending source-bound diagnosis and an attributed correction. The separate trusted-consent failure in run 1777 remains retained and unresolved. Later release directory and subsequent input gates are not established by this failed run.

## Summary The development COM1 directory probe fails after all four consent probes and development physical directory input pass. This is an original CI observation; the underlying cause and first affected revision remain unknown. ## Reproduction At Integration `c6ff552487457929b693a324990d7cf04792af74`, [original CI run 1754](https://git.erikinkinen.fi/erix/integration/actions/runs/1754) builds its pinned graph and canonical images, then invokes: ```sh ./tests/native-directory-vm.sh serial out/appliance/erix-dev.img ``` 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 retained input diagnostic is `profile=native-directory transport=serial input_exit=1 last_event=command_injected command=4`. Injection of command 4 is the last observed event, not proof of guest execution, a particular missing output or the cause. The release directory probes, editor, utility and later input gates are not reached. ## Environment and identity - Integration `c6ff552487457929b693a324990d7cf04792af74`, CI run 1754/API10376, integration job 22277, attempt 1. - Canonical development image, native x86-64 QEMU/OVMF, one virtual CPU, serial input, `native-directory` 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,389,457 bytes; their lengths and SHA-256 hashes verify with zero warning candidates. Main log SHA-256: `695690664bed8768cf9b9c5a0eef035e8f22003f628e8988dc9d879dd4f5a8db`. 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 Older original CI observation — 25 September 2026: [run1782](https://git.erikinkinen.fi/erix/integration/actions/runs/1782) at `96000d3e028173aad425f3b7029a92cca620a654` passes490/490 catalog scenarios, Rust and Markdown, then fails the development serial native-directory probe. The retained diagnostics report input_exit1 and unavailable last input event; composed vm_exit125 is not proof of a raw QEMU exit status. This matches the existing observation class without establishing its cause. No failed input was rerun. 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. Original development COM1 directory CI observation — 24 September 2026: [Run 1775](https://git.erikinkinen.fi/erix/integration/actions/runs/1775), Integration `591d96f3ffb502c65621e8eea4400041d69f622d`, API10437/job22420/attempt1, fails the development COM1 directory probe after all 489 catalog VMs, both canonical images, all four consent probes and development physical directory input pass. The receipt reports serial-input, runner 1, composed VM-command 0, serial input 1 and no requested physical cleanup. The last event is native_directory_complete at command 14. This differs from the earlier command-injected observation in [bug report #77](https://git.erikinkinen.fi/erix/integration/issues/77); a completion event does not establish successful final transport cleanup or a shared cause. Three complete original terminal logs verify: 13,387,523 bytes, matching hashes and zero warning candidates. The main log SHA-256 is `28d124214a3ee9e916c6e47b35838fccdfaa06a33c61c84b03d9cad7f1e4000e`. Rust 320/321 matrices and Markdown pass; source-bound workflow and runner blobs verify. Original 120/15/10 limits and all output/cleanup requirements remain unchanged. Raw guest/QMP artifacts are not recovered. No failed input was rerun, cause or Kernel regression attributed, or correction acceptance inferred. Report #77 remains open; master acceptance remains 15 of 460 items, weighted 3.48%. **Original development COM1 directory CI observation — run 1779, 24 September 2026.** [Run 1779](https://git.erikinkinen.fi/erix/integration/actions/runs/1779), Integration [`46ae17e84abdc1e72e89fd7c50c766c54f3bcc03`](https://git.erikinkinen.fi/erix/integration/commit/46ae17e84abdc1e72e89fd7c50c766c54f3bcc03), API10455/job22460/attempt1, fails the development COM1 directory probe. The original workflow invokes `./tests/native-directory-vm.sh serial out/appliance/erix-dev.img` after all 490 catalog VM scenarios, both canonical images, all four physical/serial consent probes and development physical directory input pass. Rust configurations with 320/321 tests, both five-test profiler ABI configurations, and Markdown also pass. The receipt reports `stage=serial-input`, runner exit 1, composed VM-command exit 0, expected VM-command exit 0, serial input exit 1, unknown physical-input status and no requested physical cleanup. Its last recorded milestone is `profile=native-directory transport=serial input_exit=1 last_event=command_injected command=5`. In the [exact selected input source](https://git.erikinkinen.fi/erix/integration/src/commit/46ae17e84abdc1e72e89fd7c50c766c54f3bcc03/scripts/native_directory_input.py), command 5 runs `ls -la tmp` and then a status-reporting command. The next maintained step waits for fresh enumeration consent for `tmp`; later steps request metadata for `tmp` and deny metadata for `tmp/..`. No fresh-consent event for command 5 appears in the summary. This source order does not establish that the guest received the command, why the observation failed, or a common cause with the earlier command-4 or command-14 observations. Three complete original terminal logs total 13,394,748 bytes with verified hashes and zero warning candidates. Main log SHA-256: `8474634f145ddaa8ded00cabd5950701e0fcf111ec956593b4e210c877c461e0`. The 11 earlier error-shaped diagnostics belong to passing negative controls; the late serial probe is the actual job failure. Original limits remain 120 seconds hard, 15 seconds stall and 10 seconds per command, with one virtual CPU. No failed input was rerun, workflow cancelled, deadline or acceptance requirement changed. Raw guest/QMP/image artifacts have not been recovered, so the composed VM-command exit is not an independently recovered raw QEMU exit. Keep this report open pending source-bound diagnosis and an attributed correction. [The separate trusted-consent failure in run 1777](https://git.erikinkinen.fi/erix/integration/issues/85) remains retained and unresolved. Later release directory and subsequent input gates are not established by this failed run.
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#77
No description provided.