Skip to content

Give the delivery fixtures room to start git - #11

Merged
AstroQore merged 1 commit into
mainfrom
fix/delivery-test-git-timeout
Aug 31, 2026
Merged

Give the delivery fixtures room to start git#11
AstroQore merged 1 commit into
mainfrom
fix/delivery-test-git-timeout

Conversation

@AstroQore

Copy link
Copy Markdown
Owner

Summary

The 0.2.0 release build failed on exactly one test — a real checkout moves from clean to dirty without fetching — with .failed(""). An empty stderr: git never reported anything because it never ran. It timed out.

The fixture helper allowed three seconds per git invocation. A loaded GitHub runner can spend longer than that just starting /usr/bin/git.

The same file already knew this. The test directly above carries a comment saying a loaded runner "can spend more than two seconds starting /usr/bin/git" and raises its own timeout to ten for that reason. The shared helper every other test goes through never got the same treatment.

  • Fixture setup now allows thirty seconds. This is test scaffolding, not a product path — the 1.5-second bound the product actually relies on lives in GitDeliveryReader and is untouched.
  • An empty stderr no longer produces a failure message that says nothing. It now names the command and the likely cause, so the next timeout is diagnosable from the CI log alone rather than by reading the helper.

Test plan

  • swift test --filter DeliverySnapshot: 5 tests green.
  • swift test: full suite green.

🤖 Generated with Claude Code

The 0.2.0 release build failed on one test: a real checkout going from
clean to dirty. The error was `.failed("")` -- an empty stderr, because
git never ran, it timed out. The fixture helper allowed three seconds for
each `git` invocation, and a loaded GitHub runner can spend longer than
that just starting /usr/bin/git.

The test immediately above it already carries a comment saying exactly
this, and already raised its own timeout to ten seconds for the same
reason. The shared helper never got the same treatment.

Fixture setup now allows thirty seconds, and an empty stderr no longer
produces a failure message that says nothing -- it names the command and
the likely cause. The 1.5-second bound the product depends on is in
GitDeliveryReader and is untouched.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-31T09:30:35.630913Z 5600ffe PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@AstroQore
AstroQore merged commit 4aa8f21 into main Aug 31, 2026
1 check passed
@AstroQore
AstroQore deleted the fix/delivery-test-git-timeout branch August 31, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant