[Asdf-devel] ASDF test failure on MKCL linux

Robert P. Goldman rpgoldman at sift.info
Mon Oct 6 21:25:14 UTC 2014

Jean-Claude Beaudoin wrote:
> On Sun, Oct 5, 2014 at 11:03 PM, Faré <fahree at gmail.com
> <mailto:fahree at gmail.com>> wrote:
>     If I replace the culprit loop (just before (DBG "Refinding test
>     successful.")) by this debugging variant, I find that the variable
>     tried-once is somehow magically reset to NIL after having been set to
>     T, and that, even if it's a defparameter instead of a lexical variable
>     (I tried both), but happily not with a defvar (where the script only
>     fails, doesn't infinitely loops). The problem is that it restarts the
>     wrong frame! Instead of resuming after the handler-bind handlers from
>     test-try-refinding.script, it resumes a frame way up there in the call
>     stack in function run-test-script in script-support.lisp, that has its
>     own handler-bind (but no restart) via macro with-test. Looks like a
>     MKCL compiler bug.

> Wow! That is bad indeed! I will try to fix it in the coming 24 hours.
> Thank you for the bug report.
>     Robert: I suggest we disable this test for MKCL until JCB fixes his
>     compiler bug, and/or use defvar as above.
> As I said here below, I may take a day or two before I have a fix for
> this one.
> So, please, do the workaround in the meantime.

I don't see the advantage of using the defvar, since it still fails,
just without looping forever.

So yes, I will disable this test on MKCL for now, and this will not be a
blocker for release. [I'm more concerned about the clisp test failures.]

More information about the asdf-devel mailing list