ASDF release candidates

Faré fahree at
Fri Mar 17 22:29:15 UTC 2017

OK, so regarding the calls to make-instance, eco needs a fix: and cl-protobufs needed a fix
(now committed, pushed).

Many of the errors are due to an old iolib. The bug was fixed in
December, but somehow quicklisp is following iolib releases rather
than the master branch. Stelian, should you make a new release? Or
should quicklisp follow master?

Otherwise, it looks mostly good. There is some breakage such as
lisp-executable on ecl, but I'll let Mark address that.

Anton, no need to test my 3.3.0 candidate anymore at the moment: I
found a blocking bug in it that I must address first.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
Reisner's Rule of Conceptual Inertia:
        If you think big enough, you'll never have to do it.

On Fri, Mar 17, 2017 at 3:36 PM, Anton Vodonosov <avodonosov at> wrote:
> I've finally build the reports.
> Sorry for the delay, it's to a large part caused by amazon simpledb glitches - it took several days to extract data.
> The lisps completed so far:
> abcl-1.4.0-fasl42-linux-x86
> ccl-1.10-r16196-f96-linux-x86
> ccl-1.11-r16635-f96-linux-x86
> ccl-1.9-r15756-f96-linux-x86
> clisp-2.49-unix-x86
> cmu-snapshot-2016-12__21b_unicode_-linux-x86
> ecl-16.1.2-unknown-linux-x86-bytecode
> ecl-16.1.2-unknown-linux-x86-lisp-to-c
> sbcl-1.1.16-linux-x86
> sbcl-1.2.6-linux-x86
> sbcl-1.3.12-linux-x86
> The full diff:
> But you must be mostly interested to see the subset where tests fail on new ASDF:
> Most of these failures are "OPERATION instances must only be created through MAKE-OPERATION"
> After filtering out these errors, this is what remains:
> SBCL 1.1.10 continues to fall into debugger as we discussed in the past (
> Best regards,
> - Anton

More information about the asdf-devel mailing list