[BUG] Native runtime-error wrapper rejects typed rejection events #136

Open
opened 2026-10-16 11:53:48 +02:00 by erikinkinen · 1 comment
Owner

Summary

The native runtime-error probe emits a valid command_rejection event, but its
enclosing shell wrapper still expects the older event sequence. It rejects a
successful probe at the final verification step.

Reproduction

Use Integration 64251db82ef8150ada5515feccab92354df2b3b8 with Exsh
835dcea2d6b55ce75599f1947c07378a2da9487c. Feed the complete event log from
the real QMP/COM1 host fixture to the Python footer in
tests/interactive-shell-lines-vm.sh, selecting native-runtime-errors.
Both transports reproduce the mismatch without booting an image.

The affected guest entry point is
tests/native-runtime-errors-vm.sh physical|serial [dev-image].

Expected and actual behavior

The wrapper should accept exactly one bounded rejection cause between the
directory command's returned prompt and completion event, while retaining
strict checks for the preceding status126 and the final sentinel.

Instead, its event-list assertion excludes command_rejection and fails.
Removing the required rejection event incorrectly lets that footer pass.
Earlier host coverage stopped at the inner disk runner and missed this final
consumer. The workflow also does not invoke either runtime-error guest route.

Environment and identity

  • Integration: 64251db82ef8150ada5515feccab92354df2b3b8.
  • Selected Exsh: 835dcea2d6b55ce75599f1947c07378a2da9487c.
  • Reproduction: Linux host, Python3.14, real Unix/QMP/COM1 fixture sockets and
    nonbootable fixture media. No genuine VM result is claimed.
  • Runtime feature: development image with its READY record, existing physical
    keyboard or COM1 input, no consent approval or new authority.
  • The typed rejection event was added in 64251db8; the older sequence had no
    such event.

Evidence and prior checks

The existing transport fixture successfully completes all eight commands and
records the typed cause before the actual wrapper footer rejects the log.
The regression fixture now executes that authored footer, rather than copying
its expected event list. Original600/90-second host bounds and120/15/10-second
guest bounds remain unchanged.

Tracking

Related: ordinary launch failure
and implementation PR.

  • Share the event contract between the probe and final wrapper.
  • Cover the actual footer with positive transport and malformed-log tests.
  • Run both development runtime-error transports in CI.
  • Demonstrate both routes in genuine VMs under the existing bounds.
## Summary The native runtime-error probe emits a valid `command_rejection` event, but its enclosing shell wrapper still expects the older event sequence. It rejects a successful probe at the final verification step. ## Reproduction Use Integration `64251db82ef8150ada5515feccab92354df2b3b8` with Exsh `835dcea2d6b55ce75599f1947c07378a2da9487c`. Feed the complete event log from the real QMP/COM1 host fixture to the Python footer in `tests/interactive-shell-lines-vm.sh`, selecting `native-runtime-errors`. Both transports reproduce the mismatch without booting an image. The affected guest entry point is `tests/native-runtime-errors-vm.sh physical|serial [dev-image]`. ## Expected and actual behavior The wrapper should accept exactly one bounded rejection cause between the directory command's returned prompt and completion event, while retaining strict checks for the preceding status126 and the final sentinel. Instead, its event-list assertion excludes `command_rejection` and fails. Removing the required rejection event incorrectly lets that footer pass. Earlier host coverage stopped at the inner disk runner and missed this final consumer. The workflow also does not invoke either runtime-error guest route. ## Environment and identity - Integration: `64251db82ef8150ada5515feccab92354df2b3b8`. - Selected Exsh: `835dcea2d6b55ce75599f1947c07378a2da9487c`. - Reproduction: Linux host, Python3.14, real Unix/QMP/COM1 fixture sockets and nonbootable fixture media. No genuine VM result is claimed. - Runtime feature: development image with its READY record, existing physical keyboard or COM1 input, no consent approval or new authority. - The typed rejection event was added in `64251db8`; the older sequence had no such event. ## Evidence and prior checks The existing transport fixture successfully completes all eight commands and records the typed cause before the actual wrapper footer rejects the log. The regression fixture now executes that authored footer, rather than copying its expected event list. Original600/90-second host bounds and120/15/10-second guest bounds remain unchanged. ## Tracking Related: [ordinary launch failure](https://git.erikinkinen.fi/erix/integration/issues/135) and [implementation PR](https://git.erikinkinen.fi/erix/integration/pulls/12). - [x] Share the event contract between the probe and final wrapper. - [x] Cover the actual footer with positive transport and malformed-log tests. - [ ] Run both development runtime-error transports in CI. - [ ] Demonstrate both routes in genuine VMs under the existing bounds.
Author
Owner

36d565b3 fixes the final verifier by sharing the live probe’s complete event and bounded cause contract. Both valid transport fixtures now pass through the actual shell footer; missing, duplicate, reordered and forged rejection events fail. All 13 focused tests pass.

Both development guest routes are scheduled in CI. Their execution and genuine guest results remain open.

`36d565b3` fixes the final verifier by sharing the live probe’s complete event and bounded cause contract. Both valid transport fixtures now pass through the actual shell footer; missing, duplicate, reordered and forged rejection events fail. All 13 focused tests pass. Both development guest routes are scheduled in CI. Their execution and genuine guest results remain open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:17 +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#136
No description provided.