Just pulled from git this afternoon and reran the tests on
ccl clisp sbcl ecl abcl allegro allegromodern
* ECL 12.12.1 fails tests test-multiple.script test-run-program.script
test-multiple:
TEST ABORTED: Subprocess run with command /bin/ln -sf
/Users/rpg/lisp/asdf/test/test-multiple.asd
23.02.2013, 08:48, Anton Vodonosov avodono...@yandex.ru:
ECL results for ASFD 2.30.5:
http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-17.html
I have reivewded the ECL results.
The (upstream) errors we have seen already on other CL implementations:
- cl-prolog
- deoxybyte-utilities
-
On 2/24/13 Feb 24 -7:05 PM, Faré wrote:
On Sun, Feb 24, 2013 at 7:14 PM, Robert Goldman rpgold...@sift.info wrote:
TEST ABORTED: Subprocess run with command /bin/ln -sf
/Users/rpg/lisp/asdf/test/test-multiple.asd
/Users/rpg/lisp/asdf/build/test-multiple-too.asd 21 exited with error
code 1
Thigs deserving attention:
- blas-complex
- blas-real
These two seem to be a problem of ASDF integration with cl:require.
To reproduce:
./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval
'(ext::install-bytecodes-compiler)' -load quicklisp-patched2/setup.lisp
-eval
Maybe the test script runner should just export SHELL=/bin/sh ?
That sounds right for the short term.
I don't claim to have fully grokked ASDF:RUN-PROGRAM yet. Would it be
reasonable to modify it so that when :force-shell is T (a) it prefers
/bin/sh to alternatives, or CMD.EXE on windows?
