-
Notifications
You must be signed in to change notification settings - Fork 110
test_sibling_enable_sameas started to FAIL on appveyor (Ubu) recently #7320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I checked the rsync version on appveyor since I couldn't reproduce it locally; leaving it here in case someone else is looking for it
|
Here's a debug log from within appveyor:
It looks like it might be this https://git-annex.branchable.com/bugs/Redundant_quote_in_the_filepath_with_rsync_remote Unsure why it only started failing now, but maybe Appveyor used to have an older rsync before (there was an Ubuntu Image Update 5 days ago). According to the git-annex bug report, git-annex version 10.20220504 has a fix for it (appveyor runs 8.20210903) |
…s xfailing on appveyor Ref: datalad#7320
FTR: |
A fix in rsync 3.2.4 broke compatibility with older annex versions. To make things a bit more complicated, ubuntu pulled that fix into their rsync package for 3.1.3-8. Adjust the test wrapper's existing skip conditions in accordingly and reenable the test. Closes datalad#7320
A fix in rsync 3.2.4 broke compatibility with older annex versions. To make things a bit more complicated, ubuntu pulled that fix into their rsync package for 3.1.3-8. Adjust the test wrapper's existing skip conditions in accordingly and reenable the test. Closes datalad#7320
A fix in rsync 3.2.4 broke compatibility with older annex versions. To make things a bit more complicated, ubuntu pulled that fix into their rsync package for 3.1.3-8. Adjust the test wrapper's existing skip conditions in accordingly and reenable the test. Closes datalad#7320
Issue fixed in |
spotted while reviewing #7318 .
looked like
and apparently not for the first time but started recently:
The text was updated successfully, but these errors were encountered: