[BUG] Runtime fixture profiles omit native build-tool settings #189

Open
opened 2026-10-24 08:47:40 +02:00 by erikinkinen · 0 comments
Owner

Summary

Four TTY fixtures and the readonly-ext fixture no longer differ from the development profile only in their declared console/storage choices. They omit native build-tool selection and workspace fields.

Reproduction

Integration CI3026 host_one fails the shared_blocks_readonly_policy assertion at f3d5b32b92; the TTY profile assertions also fail. Compare runtime.dev.toml with runtime.dev.tty-fbcon.toml, tty-serial, tty-none, tty-independent and storage-readonly-ext under tests/runtime-configs.

Expected and actual behavior

Each fixture should preserve the complete base program configuration while changing only its documented policy. The original five fixtures omit programs.sha2_tool and its 65536-byte workspace. Current development source also selects Boot with a 67108864-byte workspace, which those fixtures omit.

Environment and identity

Integration public f3d5b32b92 and current authored profile source. The failure is a deterministic host configuration comparison; guest behavior is not inferred.

Evidence and prior checks

The complete original shard log and original/current tracked TOML comparisons are retained. Normalized comparisons isolate the missing tool fields after excluding the intended console/readonly differences. Existing launch storage and session authority fields must remain intact.

Tracking

Related review: Integration PR12.

  • Give all five fixtures the same explicit native-tool selection and workspace settings as the development profile.
  • Preserve each fixture’s exact declared console/readonly differences and existing authority/storage fields.
  • Pass the unchanged strict profile-comparison controls and current host jobs.
## Summary Four TTY fixtures and the readonly-ext fixture no longer differ from the development profile only in their declared console/storage choices. They omit native build-tool selection and workspace fields. ## Reproduction [Integration CI3026 host_one](https://git.erikinkinen.fi/erix/integration/actions/runs/3026/jobs/2) fails the shared_blocks_readonly_policy assertion at f3d5b32b92ab8e5b33a6b76dc9f474ca2f1b8d04; the TTY profile assertions also fail. Compare runtime.dev.toml with runtime.dev.tty-fbcon.toml, tty-serial, tty-none, tty-independent and storage-readonly-ext under tests/runtime-configs. ## Expected and actual behavior Each fixture should preserve the complete base program configuration while changing only its documented policy. The original five fixtures omit programs.sha2_tool and its 65536-byte workspace. Current development source also selects Boot with a 67108864-byte workspace, which those fixtures omit. ## Environment and identity Integration public f3d5b32b92ab8e5b33a6b76dc9f474ca2f1b8d04 and current authored profile source. The failure is a deterministic host configuration comparison; guest behavior is not inferred. ## Evidence and prior checks The complete original shard log and original/current tracked TOML comparisons are retained. Normalized comparisons isolate the missing tool fields after excluding the intended console/readonly differences. Existing launch storage and session authority fields must remain intact. ## Tracking Related review: [Integration PR12](https://git.erikinkinen.fi/erix/integration/pulls/12). - [ ] Give all five fixtures the same explicit native-tool selection and workspace settings as the development profile. - [ ] Preserve each fixture’s exact declared console/readonly differences and existing authority/storage fields. - [ ] Pass the unchanged strict profile-comparison controls and current host jobs.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34: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#189
No description provided.