Stabilize transfer dispatch test on release runners - #97
Merged
Merged
Conversation
lukebuehler
enabled auto-merge (squash)
September 14, 2026 09:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both v0.3.0 release attempts failed in
transfer_dispatch_and_read_only_capabilities: the test allowed only one second for a journaled filesystem transfer and receivedTimeout: "transfer expired"before materialization completed.Use the existing 30-second protocol ceiling for this dispatch/access test while retaining its byte round-trip and read-only assertions. Add a deterministic expiry test that backdates an operation start, checks typed timeout errors for progress and commit, and verifies the destination is preserved. Production timeout limits and enforcement are unchanged.
Validation: all 81 native macOS environment-daemon library tests passed with
cargo test --locked -p environment-daemon --lib; formatting and whitespace checks passed. Linux coverage runs in CI.The existing v0.3.0 tag still points to the previous commit. Both failed builds stopped before artifact staging or publication; rerunning that tag alone cannot pick up this fix.