[BUG] Copied kernel harness and explicit service policies omit required inputs #104

Open
opened 2026-10-12 12:11:45 +02:00 by erikinkinen · 0 comments
Owner

Summary

Copied kernel harness and explicit service policies omit required inputs. Maintained validation cannot reach its intended successful boundary.

Reproduction

Run the maintained kernel_feature_contract_test.py, launchd_route_capacity_test.py, dynlink_manifest_catalog_test.py and fat_metadata_fixture_test.py against the linked original source. Exercise maintained runtime TOMLs with the deployment parser. The original failing source and current repairs are distinct; failures and true exit statuses are retained.

Expected and actual behavior

The maintained source should compile, discover its original controls and complete the specified checks without warnings. The isolated kernel-feature harness raises ModuleNotFoundError for deployment_tls_geometry because it copies an incomplete import closure. Twenty-five maintained runtime TOMLs omit required Loaderd stack policy. Standard service defaults omit counted Launchd/TTYD waiters. Separate manifest and FAT fixtures fail on an existing directory and a missing required root mount row.

Environment and identity

  • Component repository/revision and Integration source graph: original integration source, original Integration graph.
  • Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report.
  • Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred.
  • Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced.
  • Last known working revision, if known: not established.

Evidence and prior checks

Copy the complete actual parser import closure, state stack_bytes=65536 in the maintained explicit profiles, supply the existing 128-waiter defaults and fix fixture setup while preserving root-first mount policy. Current-source scoped validation records 62 passing host tests plus the passing copied kernel-feature harness; complete VM validation remains separate.

Original failing CI job.

Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.

Tracking

Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.

The maintained packaging and scenario controls also need these current inputs:

  • TTY packaging supplies the complete version-2, 21-word descriptor and --ttyd-waiter-records 16; readback checks waiter size, alignment, and count while retaining the 32768-byte arena assertion.
  • Shared-object registry selection checks schema 4, including the current source identity fields.
  • Realm-pipes group membership names the actual tests/scenarios/appliance-disk-image-realm-pipes-positive.toml file, resolving through the maintained runner and acceptance checker while preserving the original deadline, exit code, markers, and retirement checks.

The Launchd descriptor recurrence is tracked in issue 101. The TTY and registry fixtures were corrected in c83ffa01 and cddbfb6b. The group correction uses the real scenario pathname. The actual runner list and dynamic acceptance checker now resolve that same file; a copied bare ID cannot replace it.

## Summary Copied kernel harness and explicit service policies omit required inputs. Maintained validation cannot reach its intended successful boundary. ## Reproduction Run the maintained kernel_feature_contract_test.py, launchd_route_capacity_test.py, dynlink_manifest_catalog_test.py and fat_metadata_fixture_test.py against the linked original source. Exercise maintained runtime TOMLs with the deployment parser. The original failing source and current repairs are distinct; failures and true exit statuses are retained. ## Expected and actual behavior The maintained source should compile, discover its original controls and complete the specified checks without warnings. The isolated kernel-feature harness raises ModuleNotFoundError for deployment_tls_geometry because it copies an incomplete import closure. Twenty-five maintained runtime TOMLs omit required Loaderd stack policy. Standard service defaults omit counted Launchd/TTYD waiters. Separate manifest and FAT fixtures fail on an existing directory and a missing required root mount row. ## Environment and identity - Component repository/revision and Integration source graph: [original integration source](https://git.erikinkinen.fi/erix/integration/commit/a615de2f69c25d4575d0c349757a0017082f988b), [original Integration graph](https://git.erikinkinen.fi/erix/integration/commit/a615de2f69c25d4575d0c349757a0017082f988b). - Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report. - Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred. - Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced. - Last known working revision, if known: not established. ## Evidence and prior checks Copy the complete actual parser import closure, state stack_bytes=65536 in the maintained explicit profiles, supply the existing 128-waiter defaults and fix fixture setup while preserving root-first mount policy. Current-source scoped validation records 62 passing host tests plus the passing copied kernel-feature harness; complete VM validation remains separate. [Original failing CI job](https://git.erikinkinen.fi/erix/integration/actions/runs/2449/jobs/1). Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired. ## Tracking [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure. The maintained packaging and scenario controls also need these current inputs: - [x] TTY packaging supplies the complete version-2, 21-word descriptor and `--ttyd-waiter-records 16`; readback checks waiter size, alignment, and count while retaining the 32768-byte arena assertion. - [x] Shared-object registry selection checks schema 4, including the current source identity fields. - [x] Realm-pipes group membership names the actual `tests/scenarios/appliance-disk-image-realm-pipes-positive.toml` file, resolving through the maintained runner and acceptance checker while preserving the original deadline, exit code, markers, and retirement checks. The Launchd descriptor recurrence is tracked in [issue 101](https://git.erikinkinen.fi/erix/integration/issues/101). The TTY and registry fixtures were corrected in [c83ffa01](https://git.erikinkinen.fi/erix/integration/commit/c83ffa01e5d672f1ec1004a34fe23c7a5a773db2) and [cddbfb6b](https://git.erikinkinen.fi/erix/integration/commit/cddbfb6b922f433ba45e5022e5c01c410a11c5d8). The [group correction](https://git.erikinkinen.fi/erix/integration/commit/5cdd151b807b2e3bfc914d58c40fb7da413eb49c) uses the real scenario pathname. The actual runner list and dynamic acceptance checker now resolve that same file; a copied bare ID cannot replace it.
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#104
No description provided.