Observable outcome
The existing durable locator and golden filesystem laws execute under an owned, measured medium-test profile that enforces declared resource limits and reports which limit failed. This is the bounded follow-up for PR #179's process-isolation change; any landing waiver requires explicit maintainer approval and expiry, not this issue's existence.
Owner: @flyingrobots.
Scope
Cover the durable_locator and golden_file_worldline integration-test executables, their child processes, and their existing runtime assertions. Record immutable build, commands, platform, owned scratch locations, deadlines, memory limits, permitted subprocesses, network restrictions, artifact destinations, suite latency budget and enforcing mechanism. Measure baseline behavior before setting budgets and retain rationale for headroom.
Exclude changing Keep runtime locks, retrying flaky laws into green, source-string/count tests, a repository-wide testing framework rewrite, or unrelated test suites. This work has no implementation prerequisite on documentation-tool profile issue #177; shared policy alone does not establish a dependency.
Acceptance
- The profile runs both existing executables in debug/release on supported Linux ext4 and preserves all typed and byte-output oracles.
- Deadline/memory/network controls cover child processes and are enforced rather than declared only; faulted execution demonstrably reports the violated boundary and preserves diagnostic evidence.
- Scratch ownership and cleanup remain isolated between concurrent workers.
- CI applies the reviewed profile to these tests, with no retry-to-green or hidden allow-failure path.
- Profile metadata includes measurements, owner and expiry/disposition for any remaining gap; remove the scoped waiver after independent review and green final checks.
Safe intermediate state: #179's process separation remains intact while the profile adds enforcement. This is one executable test-runner outcome, not a tracker epic or a count of product recovery claims.
Observable outcome
The existing durable locator and golden filesystem laws execute under an owned, measured medium-test profile that enforces declared resource limits and reports which limit failed. This is the bounded follow-up for PR #179's process-isolation change; any landing waiver requires explicit maintainer approval and expiry, not this issue's existence.
Owner: @flyingrobots.
Scope
Cover the
durable_locatorandgolden_file_worldlineintegration-test executables, their child processes, and their existing runtime assertions. Record immutable build, commands, platform, owned scratch locations, deadlines, memory limits, permitted subprocesses, network restrictions, artifact destinations, suite latency budget and enforcing mechanism. Measure baseline behavior before setting budgets and retain rationale for headroom.Exclude changing Keep runtime locks, retrying flaky laws into green, source-string/count tests, a repository-wide testing framework rewrite, or unrelated test suites. This work has no implementation prerequisite on documentation-tool profile issue #177; shared policy alone does not establish a dependency.
Acceptance
Safe intermediate state: #179's process separation remains intact while the profile adds enforcement. This is one executable test-runner outcome, not a tracker epic or a count of product recovery claims.