fix(eval): run tar with relative paths so the SWE-chat harness works on Windows - #164
Merged
kushalpatil07 merged 1 commit intoJul 29, 2026
Conversation
…on Windows GNU tar interprets absolute Windows paths (C:\...) in -f/-C as remote host specs and exits with 'Child returned status 128', so prepareTargetRepo failed for every runner on Windows. Invoke tar from the run directory with paths relative to it instead; behavior on Unix is unchanged. Verified: --fixture-only now completes on Windows (previously failed at extraction) and typecheck/build are clean.
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
2 participants
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.
While building the notes benchmark arm (#160) I hit the SWE-chat harness failing on Windows at the base-archive extraction step for every runner, including
baseline --fixture-only:Cause: GNU tar interprets absolute Windows paths (
C:\...) passed to-f/-Cas remote host specs (host:path).prepareTargetRepoinrun.tsandbuild-memory.tspasses both the archive path and the extract dir as absolute paths.Fix: invoke tar from the run directory with paths relative to it. No behavior change on Unix; no GNU-specific flags (
--force-localwould break bsdtar on macOS).Verified on Windows:
--runner baseline --fixture-onlynow completes ("Fixture prep passed") where it previously crashed at extraction;npm run typecheckandnpm run buildclean;git diff --checkclean.Note:
scripts/memory-build/collect-repo-snapshot.tshas the same pattern — left untouched to keep this scoped to the eval harness, happy to fix it there too if wanted.