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

Added a comment

Browse source
This commit is contained in:
jkniiv 2023-03-05 20:18:02 +00:00 committed by admin
parent 4b1a7e4d9e
commit f9deee36c7
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/bugs/windows_build_fails_starting_from_commit_54ad1b4cf/comment_2_bd9a77da095bffdcd3ed30e08192b9d2._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="jkniiv"
avatar="http://cdn.libravatar.org/avatar/05fd8b33af7183342153e8013aa3713d"
subject="comment 2"
date="2023-03-05T20:18:01Z"
content="""
On a positive note I can confirm that my compiled versions of commits 54ad1b4cf and 398633c12
pass their test suite even in a subdirectory some 64 characters deep (for instance in a directory
named like `c:/Users/jkniiv/annx/annx.10.20230228-g505f1a654--test-test-test`) whereas the commit
just prior to \"Windows: Support long filenames in more (possibly all) of the code\" (54ad1b4cf), or
505f1a654, fails some one third to one half of its tests in said directory. Shortening the test
directory name to say `c:/Users/jkniiv/annx/annx` allows the test suite to pass in older versions
of git-annex all other things considered equal. So far I have been running the built-in tests
always in 'c:/annx' (/c/annx in Git Bash) but here on forward I'll probably start using a deeper
path somewhere in my user folder / home directory just to catch possible future regressions in long
path handling. In any case, @Joey, congratulations 🎉 are in order for your fine achievement from
a Windows user point of view. :)
"""]]