Keep read-only runtime fixture policy explicit #398

Open
erikinkinen wants to merge 5 commits from feature/runtime-fixture-policy-consistency into feature/vfs-namespace-cancellation
Owner

Declare the disabled C startup program in the read-only ext fixture so its complete policy differs from the product profile only by the original mount’s read-only flag.

Cover every maintained runtime profile as admitted policy or its exact intended topology refusal. Keep the FAT-only and no-input fixtures as negatives, verify that rejection preserves destinations, and retain the existing five native-tool workspace declarations and distinct TTY seat policies.

Depends on #397.

Declare the disabled C startup program in the read-only ext fixture so its complete policy differs from the product profile only by the original mount’s read-only flag. Cover every maintained runtime profile as admitted policy or its exact intended topology refusal. Keep the FAT-only and no-input fixtures as negatives, verify that rejection preserves destinations, and retain the existing five native-tool workspace declarations and distinct TTY seat policies. Depends on [#397](https://git.erikinkinen.fi/erix/integration/pulls/397).
erikinkinen added this to the Alpha 1 milestone 2026-11-06 11:59:28 +01:00
fix: Preserve explicit read-only runtime fixture policy
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
CI / markdown (push) Successful in 8s
Coreutils provider graph / coreutils (push) Failing after 27s
CI / rust (push) Successful in 3m39s
CI / host_one (push) Failing after 5m49s
CI / host_zero (push) Failing after 21m29s
CI / integration (push) Has been skipped
35a2c146f3
Keep the read-only ext fixture identical to product policy except its original mount flag by declaring the disabled C startup entry. Classify every maintained profile as admitted policy or its exact intended topology refusal, without adding hardware, services or parser bypasses.
test: Isolate native feature forwarding from runtime intake
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
CI / markdown (push) Successful in 21s
CI / rust (push) Failing after 59s
Coreutils provider graph / coreutils (push) Failing after 40s
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / integration (push) Has been cancelled
1f67681769
Observe the runtime selection passed to the shared-object builder without
starting an unrelated native source acquisition in the CLI forwarding test.
ci: Use shared development dependency profiles
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / integration (push) Has been cancelled
CI / markdown (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
a3f9912489
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Separate Markdown checks from the build workflow
Some checks failed
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / rust (push) Has been cancelled
CI / host_zero (push) Has been cancelled
CI / host_one (push) Has been cancelled
CI / integration (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
Markdown / markdown (push) Has been cancelled
521dc9a77a
Keep each workflow below the repository size limit by giving Markdown its own file. Preserve event filters, job conditions and command bodies, with independent concurrency for the Markdown workflow.
ci: Use shared development dependency profiles
Some checks failed
Markdown / markdown (push) Successful in 10s
Coreutils provider graph / coreutils (push) Failing after 40s
CI / rust (push) Successful in 6m6s
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / host_one (push) Failing after 6m41s
CI / host_zero (push) Failing after 23m39s
CI / integration (push) Has been skipped
00778f2bc6
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
Some checks failed
Markdown / markdown (push) Successful in 10s
Coreutils provider graph / coreutils (push) Failing after 40s
CI / rust (push) Successful in 6m6s
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
Coreutils provider graph / coreutils (pull_request) Has been skipped
Markdown / markdown (pull_request) Has been skipped
CI / host_one (push) Failing after 6m41s
CI / host_zero (push) Failing after 23m39s
CI / integration (push) Has been skipped
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/runtime-fixture-policy-consistency:feature/runtime-fixture-policy-consistency'
git switch 'feature/runtime-fixture-policy-consistency'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/vfs-namespace-cancellation'
git merge --no-ff 'feature/runtime-fixture-policy-consistency'
git switch 'feature/runtime-fixture-policy-consistency'
git rebase 'feature/vfs-namespace-cancellation'
git switch 'feature/vfs-namespace-cancellation'
git merge --ff-only 'feature/runtime-fixture-policy-consistency'
git switch 'feature/runtime-fixture-policy-consistency'
git rebase 'feature/vfs-namespace-cancellation'
git switch 'feature/vfs-namespace-cancellation'
git merge --no-ff 'feature/runtime-fixture-policy-consistency'
git switch 'feature/vfs-namespace-cancellation'
git merge --squash 'feature/runtime-fixture-policy-consistency'
git switch 'feature/vfs-namespace-cancellation'
git merge --ff-only 'feature/runtime-fixture-policy-consistency'
git switch 'feature/vfs-namespace-cancellation'
git merge 'feature/runtime-fixture-policy-consistency'
git push origin 'feature/vfs-namespace-cancellation'
Sign in to join this conversation.
No description provided.