WIP: Include scenario parser policy in the fixture chain #501

Draft
erikinkinen wants to merge 5 commits from feature/scenario-harness-policy-closure into feature/block-fixture-source-cleanliness
Owner

The detached bootloader timeout fixture needs the parser’s local heap policy module. Compose #494 with #500 so scenario parsing reaches the timeout assertions.

  • Include the parser’s policy dependency.
  • Preserve the existing six timeout assertions.
  • Complete integration CI.
The detached bootloader timeout fixture needs the parser’s local heap policy module. Compose [#494](https://git.erikinkinen.fi/erix/integration/pulls/494) with [#500](https://git.erikinkinen.fi/erix/integration/pulls/500) so scenario parsing reaches the timeout assertions. - [x] Include the parser’s policy dependency. - [x] Preserve the existing six timeout assertions. - [ ] Complete integration CI.
erikinkinen added this to the Alpha 1 milestone 2026-11-07 05:15:29 +01:00
test: Include heap policy in detached scenario harness
Some checks failed
CI / host_two (push) Has been skipped
CI / integration (push) Has been skipped
Coreutils provider graph / coreutils (push) Successful in 3m23s
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (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 11s
CI / rust (push) Failing after 44s
CI / host_three (push) Has been skipped
CI / host_one (push) Has been skipped
CI / host_zero (push) Has been skipped
89794b37c8
Copy the parser's actual local semantic-policy dependency into the bootloader
timeout fixture. Its transitive imports are standard-library only; keep the
literal harness inputs, original timeout assertions and parser validation intact.
build: compose scenario harness policy inputs
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 / host_two (pull_request) Has been skipped
CI / host_three (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 11s
Coreutils provider graph / coreutils (push) Successful in 3m45s
CI / rust (push) Successful in 5m6s
CI / host_one (push) Successful in 11m31s
CI / host_three (push) Successful in 12m50s
CI / host_two (push) Successful in 12m58s
CI / host_zero (push) Successful in 15m51s
CI / integration (push) Failing after 11m22s
70fd5052a4
Include the detached scenario parser policy dependency alongside the current Cargo and block fixture corrections. Preserve the existing timeout expectations and keep the original feature branches available independently.
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 / host_two (pull_request) Has been skipped
CI / host_three (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 / host_two (push) Has been cancelled
CI / host_three (push) Has been cancelled
CI / integration (push) Has been cancelled
CI / markdown (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
e95f89cdbf
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 / host_two (pull_request) Has been skipped
CI / host_three (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 / host_two (push) Has been cancelled
CI / host_three (push) Has been cancelled
CI / integration (push) Has been cancelled
Coreutils provider graph / coreutils (push) Has been cancelled
Markdown / markdown (push) Has been cancelled
45134af56b
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
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (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
Markdown / markdown (push) Successful in 15s
Coreutils provider graph / coreutils (push) Successful in 4m36s
CI / rust (push) Successful in 7m30s
CI / host_one (push) Successful in 18m15s
CI / host_two (push) Successful in 19m25s
CI / host_three (push) Successful in 19m56s
CI / host_zero (push) Failing after 23m0s
CI / integration (push) Has been skipped
71893ac2b2
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
CI / rust (pull_request) Has been skipped
CI / host_zero (pull_request) Has been skipped
CI / host_one (pull_request) Has been skipped
CI / host_two (pull_request) Has been skipped
CI / host_three (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
Markdown / markdown (push) Successful in 15s
Coreutils provider graph / coreutils (push) Successful in 4m36s
CI / rust (push) Successful in 7m30s
CI / host_one (push) Successful in 18m15s
CI / host_two (push) Successful in 19m25s
CI / host_three (push) Successful in 19m56s
CI / host_zero (push) Failing after 23m0s
CI / integration (push) Has been skipped
This pull request has changes conflicting with the target branch.
  • tests/run-scenario-bootloader-negative-timeout.sh
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

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

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/block-fixture-source-cleanliness'
git merge --no-ff 'feature/scenario-harness-policy-closure'
git switch 'feature/scenario-harness-policy-closure'
git rebase 'feature/block-fixture-source-cleanliness'
git switch 'feature/block-fixture-source-cleanliness'
git merge --ff-only 'feature/scenario-harness-policy-closure'
git switch 'feature/scenario-harness-policy-closure'
git rebase 'feature/block-fixture-source-cleanliness'
git switch 'feature/block-fixture-source-cleanliness'
git merge --no-ff 'feature/scenario-harness-policy-closure'
git switch 'feature/block-fixture-source-cleanliness'
git merge --squash 'feature/scenario-harness-policy-closure'
git switch 'feature/block-fixture-source-cleanliness'
git merge --ff-only 'feature/scenario-harness-policy-closure'
git switch 'feature/block-fixture-source-cleanliness'
git merge 'feature/scenario-harness-policy-closure'
git push origin 'feature/block-fixture-source-cleanliness'
Sign in to join this conversation.
No description provided.