[BUG] Launchd filesystem packaging fixture uses retired capacity layout #101

Closed
opened 2026-10-01 21:35:49 +02:00 by erikinkinen · 0 comments
Owner

Summary

The Launchd filesystem-packaging fixture embeds retired capacity-layout version 7
with 28 words. The existing image model requires version 8 with 30 words, including
the independent authority-row size/alignment pair. The fixture therefore cannot
exercise the intended current Launchd image-layout contract.

Reproduction

At Integration revision 00a17bcea0bb415d1b283c78998d9071a5334e02, inspect
tests/launchd-filesystem-packaging.sh: its metadata ELF encodes <28Q> beginning
with 7, 1 and its readback requests 28 words. Compare
scripts/launchd_state_capacity.py, whose current constants are version 8 and 30
words. The fixture also omits the independent authority-row layout pair.

Run bash tests/launchd-filesystem-packaging.sh from a checkout with
its documented dependencies. The original report identified the mismatch by
source inspection.

Expected and actual behavior

Expected: the authored fixture supplies the complete current target descriptor,
then verifies the packaged arena against its explicit storage policy.

Actual source: the fixture supplies an obsolete version and an incomplete word
count. The current model rejects retired target descriptors before the intended
packaging assertions can be reached. No observed exit status or log is available.

Environment and identity

  • Component repository/revision and Integration source graph: Integration 00a17bcea0bb415d1b283c78998d9071a5334e02; authored host fixture and image model.
  • Image profile, digest and build/runtime configuration: synthetic Launchd metadata ELF; no new image built.
  • Hardware or VM, architecture, firmware and toolchain versions: host source inspection only; no VM execution.
  • Input/session route and granted authority relevant to reproduction: host fixture inputs only; no runtime grant or consent boundary is involved.
  • Last known working revision, if known: not established.

Evidence and prior checks

Fixture source
and image model
show the original mismatch.

Tracking

Repair the literal descriptor, complete geometry and exact arena expectations
while migrating counted retained program storage. Related:
Launchd#1,
Integration PR12,
Phase 6 tracker.

Resolution

The earlier version-9/30-word correction is retained in
66d3ec99.

The same fixture drift recurred when the Launchd capacity descriptor gained counted waiter storage. The current fixture must use version 10 with 33 words and supply --launchd-waiter-records 16. Its readback must check the waiter size, alignment, and count (32, 8, 16) while retaining the 32768-byte arena assertion.

Commit 24d671e7 updates the literal descriptor and explicit waiter input.

## Summary The Launchd filesystem-packaging fixture embeds retired capacity-layout version 7 with 28 words. The existing image model requires version 8 with 30 words, including the independent authority-row size/alignment pair. The fixture therefore cannot exercise the intended current Launchd image-layout contract. ## Reproduction At Integration revision `00a17bcea0bb415d1b283c78998d9071a5334e02`, inspect `tests/launchd-filesystem-packaging.sh`: its metadata ELF encodes `<28Q>` beginning with `7, 1` and its readback requests 28 words. Compare `scripts/launchd_state_capacity.py`, whose current constants are version 8 and 30 words. The fixture also omits the independent authority-row layout pair. Run `bash tests/launchd-filesystem-packaging.sh` from a checkout with its documented dependencies. The original report identified the mismatch by source inspection. ## Expected and actual behavior Expected: the authored fixture supplies the complete current target descriptor, then verifies the packaged arena against its explicit storage policy. Actual source: the fixture supplies an obsolete version and an incomplete word count. The current model rejects retired target descriptors before the intended packaging assertions can be reached. No observed exit status or log is available. ## Environment and identity - Component repository/revision and Integration source graph: Integration `00a17bcea0bb415d1b283c78998d9071a5334e02`; authored host fixture and image model. - Image profile, digest and build/runtime configuration: synthetic Launchd metadata ELF; no new image built. - Hardware or VM, architecture, firmware and toolchain versions: host source inspection only; no VM execution. - Input/session route and granted authority relevant to reproduction: host fixture inputs only; no runtime grant or consent boundary is involved. - Last known working revision, if known: not established. ## Evidence and prior checks [Fixture source](https://git.erikinkinen.fi/erix/integration/src/commit/00a17bcea0bb415d1b283c78998d9071a5334e02/tests/launchd-filesystem-packaging.sh) and [image model](https://git.erikinkinen.fi/erix/integration/src/commit/00a17bcea0bb415d1b283c78998d9071a5334e02/scripts/launchd_state_capacity.py) show the original mismatch. ## Tracking Repair the literal descriptor, complete geometry and exact arena expectations while migrating counted retained program storage. Related: [Launchd#1](https://git.erikinkinen.fi/erix/launchd/issues/1), [Integration PR12](https://git.erikinkinen.fi/erix/integration/pulls/12), [Phase 6 tracker](https://git.erikinkinen.fi/erix/integration/issues/65). ## Resolution The earlier version-9/30-word correction is retained in [66d3ec99](https://git.erikinkinen.fi/erix/integration/commit/66d3ec99af30e16847b5a9011dab47c3df0086d2). The same fixture drift recurred when the Launchd capacity descriptor gained counted waiter storage. The current fixture must use version 10 with 33 words and supply `--launchd-waiter-records 16`. Its readback must check the waiter size, alignment, and count `(32, 8, 16)` while retaining the 32768-byte arena assertion. [Commit 24d671e7](https://git.erikinkinen.fi/erix/integration/commit/24d671e723d6a0a5298baf577063a978782729b2) updates the literal descriptor and explicit waiter input.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39: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#101
No description provided.