You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The failure probe asserts that no primary, bare-repository, or empty-root fixture paths are created or named after both allocation forms fail. No user machine configuration or global cleanup was changed.
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.
Fresh-context review record (coordinator, 2026-09-06; read-only Opus 5 reviewer over the diff against the merge base; route: the standing D-12 rule for Codex-session PRs — review, fix MEDIUM+ in-PR, merge, disposition comment).
VERDICT: SHIP, nothing fixed in-PR. The destructive-path checks come back clean: every rm -rf -- "$FIXTURE_ROOT" is fenced by empty/not-a-directory guards with -- and no trailing slash, the trap early-returns on an empty root, and the old FIXTURE_ROOT="" path really would have run git init "/primary" at the filesystem root, so the fix is real; the failure path exits non-zero through FAIL. LOWs recorded for #1855: three new knobs undocumented in the usage header; an ambient WT_GUARD_ALLOCATE_ONLY makes the suite exit 0 silently having run zero cases; a non-numeric value prints integer expression expected; a noexec temp mount would fail both probes spuriously (hypothesis; no CI caller). Hosted Windows red at the previous head was the #2378 launcher-suite class; the branch is updated past #2608.
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
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.
Summary
mktemp -dforms before deriving any fixture child pathVerification
bash -n scripts/worktree_guard.tests.sh— passedbash scripts/worktree_guard.tests.sh— 38 passed, 0 failed, 0 skippedgit diff --check— passedThe failure probe asserts that no primary, bare-repository, or empty-root fixture paths are created or named after both allocation forms fail. No user machine configuration or global cleanup was changed.
Refs #1855