Closed stain closed 6 years ago
This is most likely due to your git client converting the existing LF terminators in the test bag tag files to CRLF on checkout. I just validated the tests do complete on my Win10 system provided the line terminators don't get modified.
See this thread for some more insight: https://stackoverflow.com/questions/2517190/how-do-i-force-git-to-use-lf-instead-of-crlf-under-windows
I'm going to add a .gitattributes file to the repo with the setting * text=auto eol=lf
, hopefully that works for most people doing checkouts on Windows without having to modify their local git config.
I just tested this with the latest code and a fresh virtualenv on Win10 and could not reproduce, so it looks like the .gitattributes
file with the * text=auto eol=lf
setting is doing the right thing. @stain if you have a spare bit of time and could confirm, that would great.
Thanks, @mikedarcy - I can confirm that in a fresh checkout python setup.py test
works well in my Windows 10, also for the 1.2.4 release.
However in the old git checkout the same tests fails, even after git reset --hard
-- so a good trick for anyone affected is to do a clean checkout.
test_validate_complete_bag_full
,test_resolve_fetch_ark
,test_resolve_fetch_http
andtest_validate
fail on Windows 10.with a fresh
virtualenv
enviroment and fresh pip installs.Stacktrace
It seems errors are all in tag files - are the
.txt
files written with CR+LF on Windows but the tests experting checksums based on LF?