[BUG] Native build capture loses earlier stdout output #95

Closed
opened 2026-09-25 13:15:44 +02:00 by erikinkinen · 0 comments
Owner

Summary

Closed as invalid. The coordinator misread the combined display of consecutive stdout and stderr tail commands as stdout alone. The allegedly lost build progress remains in the original stderr. No stream loss or source defect was established.

Reproduction

Read the two retained streams separately for Integration 3bfa40a6978bd9fc811055ad4c89e8d506f7077c. Stdout is 106 bytes containing three final validators. Stderr is 35,691 bytes and contains scenario admission, Rootd/Kernel/Exsh/byte-client build progress, packaging and final VM/marker success. The scripts explicitly emit build progress to stderr.

Expected and actual behavior

Both original streams retain their intended output and contain zero warning candidates. There was no independently measured nonzero initial stdout size. The previous claim that stdout was truncated was an interpretation error, not a reproduced defect. No code change is required.

Environment and identity

  • Integration: 3bfa40a6978bd9fc811055ad4c89e8d506f7077c and its original complete catalog.
  • Native scenario: configured byte clients, unchanged 120/45-second guest bounds, Procd38/Pagerd102.
  • Original result: exit zero, acknowledged cleanup, 109 hashed artifacts and 57,045 serial bytes.

Evidence and prior checks

The original native streams and all guest artifacts remain preserved. Source emission sites in scripts/lib/service-build.sh and the dynamic artifact builders explain the stderr placement. Two additional build-only diagnostics launched no VM; the broader trace exceeded its declared output budget and is retained as a diagnostic failure. It provides no acceptance credit and does not invalidate the original native result.

Tracking

The actual RTC inventory defect is issue 94. The incorrect capture claim is retracted from the phase tracker and affected PRs. Future reviews must label each captured stream explicitly.

## Summary Closed as invalid. The coordinator misread the combined display of consecutive stdout and stderr tail commands as stdout alone. The allegedly lost build progress remains in the original stderr. No stream loss or source defect was established. ## Reproduction Read the two retained streams separately for Integration `3bfa40a6978bd9fc811055ad4c89e8d506f7077c`. Stdout is 106 bytes containing three final validators. Stderr is 35,691 bytes and contains scenario admission, Rootd/Kernel/Exsh/byte-client build progress, packaging and final VM/marker success. The scripts explicitly emit build progress to stderr. ## Expected and actual behavior Both original streams retain their intended output and contain zero warning candidates. There was no independently measured nonzero initial stdout size. The previous claim that stdout was truncated was an interpretation error, not a reproduced defect. No code change is required. ## Environment and identity - Integration: `3bfa40a6978bd9fc811055ad4c89e8d506f7077c` and its original complete catalog. - Native scenario: configured byte clients, unchanged 120/45-second guest bounds, Procd38/Pagerd102. - Original result: exit zero, acknowledged cleanup, 109 hashed artifacts and 57,045 serial bytes. ## Evidence and prior checks The original native streams and all guest artifacts remain preserved. Source emission sites in `scripts/lib/service-build.sh` and the dynamic artifact builders explain the stderr placement. Two additional build-only diagnostics launched no VM; the broader trace exceeded its declared output budget and is retained as a diagnostic failure. It provides no acceptance credit and does not invalidate the original native result. ## Tracking The actual RTC inventory defect is [issue 94](https://git.erikinkinen.fi/erix/integration/issues/94). The incorrect capture claim is retracted from the [phase tracker](https://git.erikinkinen.fi/erix/integration/issues/65) and affected PRs. Future reviews must label each captured stream explicitly.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:18 +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#95
No description provided.