mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comments

Browse source
This commit is contained in:
Joey Hess 2015-07-07 14:50:47 -04:00
parent 625303226d
commit 202f9bf06a
2 changed files with 16 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_1_014466c5da1922d34a498648baeeba26._comment
View file

@ -3,15 +3,7 @@
subject="""comment 1""" subject="""comment 1"""
date="2015-07-07T17:23:51Z" date="2015-07-07T17:23:51Z"
content=""" content="""
Is the "mv" error message part of the output around the failing addurl
test, or the failing import test? Not clear from your paste.
The "cannot move" message is not an error message from an external "mv" The "cannot move" message is not an error message from an external "mv"
command. This error comes from Win32.moveFileEx, which fails on cross-device command. This error comes from Win32.moveFileEx, which fails on cross-device
renames. renames.
Of course, import is supposed to work across devices, and the code
calls `moveFile`, which is supposed to catch rename errors and fall
back to an external mv command. Seems that fallback is not working on
Windows.
"""]] """]]

16
doc/bugs/git_annex_test_fails_when_run_through_powershell/comment_2_241ab999007eecaa2cd5a854e722e315._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2015-07-07T18:15:21Z"
content="""
The import problem can be reproduced by running git annex import on a different
drive in Windows. No powershell needed; it does fall back to the external
mv command, but that fails for some reason. Was unable to determine why
(running the same mv at the command line works ok). Fixed for Windows by
avoiding using the external mv command there.
Still need more details about the addurl failure. AFAICS, it does not
involve "mv" at all. Probably it involves
the generated file:// url not working for some reason.
What drive and path did you run the test suite in?
"""]]