Skip to content

win32: return 23 from a pull that could not write a file - #4

Open
nikitatsym wants to merge 2 commits into
nuket:windows-cmake-portfrom
nikitatsym:fix-receiver-exit-status
Open

nikitatsym wants to merge 2 commits into
nuket:windows-cmake-portfrom
nikitatsym:fix-receiver-exit-status

Conversation

@nikitatsym

@nikitatsym nikitatsym commented Oct 1, 2026 •

Copy link
Copy Markdown

When a pull into Windows cannot write or rename a file, rsync prints the error but exits with 0 instead of 23. The receiver runs as a thread here and the thread always ended with status 0, while on POSIX the forked receiver exits with 23. This change ends the receiver thread with the same status, and a new exit_codes test checks both push and pull. It also gives keep.txt a fixed mtime in test_batch.py, because that test raced on the clock and the new exit status turns the race into a failure.

@nikitatsym
nikitatsym force-pushed the fix-receiver-exit-status branch from 573b110 to 433cfea Compare October 1, 2026 17:28
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