While testing on Windows, two tests revealed a bug in ABCL: test-nested-components.script test-system-pathnames.script Unsupported case in TRANSLATE-DIRECTORY-COMPONENTS. Is there a good way to get a useful backtrace? We used: (let ((*debug-io* stream)) (top-level::backtrace-command count)) and it yielded no output (count bound to nil, stream to the log file).
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The Keyboard is mightier than the Death Ray...
On Tue, Oct 22, 2013 at 2:26 PM, Faré fahree@gmail.com wrote:
Testing ASDF found several bugs in ABCL.
cd ~/cl/asdf/
abcl --noinform --eval '(or`#.(load(string`|test/script-support.lisp|)`:verbose():print())#.(asdf-test::exit-lisp`0))' Failed to require LOOP because 'Illegal function object: (bqv).'
Maximum error depth exceeded (11 nested errors) with 'Illegal function object: (bqv).'.
abcl --noinform --eval "(or'#.(load(string'|test/script-support.lisp|):verbose():print())#.(asdf-test::exit-lisp'0))"
So your backquote parser is broken somehow.
Also, upgrading from ASDF 2.25 or 2.26 used to work, but not anymore. Now 2.27 is needed (as configured in header.lisp, and tested with make u l=abcl ASDF_UPGRADE_TEST_TAGS=2.25).
Finally, there are many instances of abcl in #+ or #- in the test/ directory, including two new ones in test-bundle on Mac (which is a regression from abcl 1.1.0) and in test-stamp-propagation (which is a new test, and a bug shared with XCL).
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Not all Law is created equal before Man. Some Law causes least conflict and least perverse incentives. By definition we call it Natural Law.