[asdf-devel] testing ASDF with cl-test-grid

[Faré]

On Tue, Feb 19, 2013 at 9:08 AM, Anton Vodonosov <avodonosov at yandex.ru> wrote:
>> unicly: encoding problem. I wonder why it doesn't appear with other
>> run — are you using an ASCII locale where you were using UTF-8 before?
>
> No, it was run with ASCII both times. The difference turns out
> is :verbose t passed into (ql:quickload). [...]
>
> As I see in the Quicklisp sources, The :verbose nil binds some
> variables like cl:*load-verbose* and invokes cl:muffle-warning
> restart from handler-bind. Probably this interferes somehow with
> ASDF.
>
Oh. Then it's not an ASDF issue, and the issue should be there
using old versions of ASDF, too, whenever quickload is verbose
and doesn't muffle these warnings.
The real solution is to use UTF-8.

Which reminds me, we should test with
(setf asdf:*default-encoding* :utf-8) at some point,
and also without (setf asdf:*warnings-file-type* nil).

>> deoxybytes-*, cl-prolog: WFM. Maybe it's looks like it's been fixed by
>> 2.29.1??? Or maybe you're actually using 2.28.10?? This looks more
>> like the bug I fixed in 2.28.11 aka 2.29.
>
> No, it was definetely tested with 2.29:
>
The mind boggles. Oh well, as long as the bug is gone with the latest ASDF,
that should be fine.

> If remaining libraries are upstream errors, we can perform another
> test run with 2.29.2 to see ensure we have no other errors, and the
> checkout these libraries to quicklisp/local-projects and test again
> to ensure they are fixed upstream.
>
I've contacted all upstream authors for the previously found bugs.
Only a few did respond already.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
There are three types of people in the world;
those who can count, and those who can't.