I have started cl-test-grid tests with the latest ASDF (git revision 38337a5)
After SBCL and CCL tests complete we can run tests on the previous ASDF
and compare results.

The question: what is the previous stable and tested ASDF version?

Best regards,
- Anton


27.12.2013, 17:34, "Mark Evenson" <even...@panix.com>:
> On Dec 20, 2013, at 22:34, Mark Evenson <even...@panix.com> wrote:
>
> […]
>
>>  It isn’t quite clear how to run the tests under Windows.  I am using 
>> Cygwin, so I thought I could just ensure that ‘abcl’ is in my path and 
>> symlinked to ‘abcl.bat
>>
>>          cygwin-bash$ sh run-tests.sh abcl
>>
>>  but I get an “access is denied” message, which is odd as I can invoke 
>> `abcl` directly.  Probably some faulty understanding on my part of cygwin v. 
>> DOS scripting.
>
> A couple of notes on running ASDF tests under Windows:
>
> 1.  The “Access is denied” message comes from problems with mismatched NTFS 
> permissions.  I think it was the result of using “hg clone" in the Windows 
> "System Administrator” role which creates directories don’t automatically 
> have all necessary permissions for writes.  Or something.  The solution for 
> me was to use the “Edit” dialog accessed “Properties >> Security” popup from 
> Windows Explorer to recursively set “Full Control” for “Everyone” from the 
> root `asdf` folder.  Those who wish to contribute a more nuanced 
> understanding of what Windows is trying to protect against are invited to 
> explain in a more articulate manner the more proper set of restricted 
> permissions to grant.
>
> 2.  Using cygwin, one cannot get ‘test/run-tests.sh’ to use the ‘abcl.bat’ 
> Windows batch script to invoke ABCL, as it fails with problems in escaping 
> the VERTICAL_LINE (#\|) from some being interpreted as a pipe operation by 
> some part of the invocation chain.  The solution is to use the Bourne-shell 
> ‘abcl’ invocation script.
>
> More soon…
>
> --
> "A screaming comes across the sky.  It has happened before but there is 
> nothing
> to compare to it now."

Reply via email to