Dave Cooper wrote:
No, you ran this test today, but it uses 3.1.0.35, and the test doesn't trace the requested functions. You might have run it from a different directory than you extracted the asdf code. Please try again with the latest ASDF (3.1.0.72 or whatever).Completely and extremely my bad.
Please see here for the results with 3.1.0.72 (errors for clisp and one for sbcl -- Allegros are passing now thanks to your fix):
https://dl.dropboxusercontent.com/u/19667598/asdf-failures/3.1.0.72/sbcl-tes...
This looks like a bug in SBCL. Here's the test failure:
These two expressions yield paths that are not pathname-equal the first expression ASDF-TEST:*TEST-DIRECTORY* yields this: #P"C:/Users/dcooper8/genworks/cl/tests/asdf/asdf-windows/test/" (:HOST #<SB-IMPL::WIN32-HOST {22472481}> :DEVICE "C" :DIRECTORY (:ABSOLUTE "Users" "dcooper8" "genworks" "cl" "tests" "asdf" "asdf-windows" "test") :NAME NIL :TYPE NIL :VERSION NIL)
the other expression (UIOP/OS:GETCWD) yields that: #P"C:/users/dcooper8/genworks/cl/tests/asdf/asdf-windows/test/" (:HOST #<SB-IMPL::WIN32-HOST {22472481}> :DEVICE "C" :DIRECTORY (:ABSOLUTE "users" "dcooper8" "genworks" "cl" "tests" "asdf" "asdf-windows" "test") :NAME NIL :TYPE NIL :VERSION NIL) Script failed
Should we be treating Windows filenames as case-insensitive?
According to Stack Overflow, NTFS can be configured to be case-sensitive, but typically isn't.
Maybe PATHNAME-EQUAL should case-flatten (string-equal) on Windows?