Windows problems: moratorium continues

Elias Pipping pipping.elias at
Wed Sep 14 14:27:24 UTC 2016

> On 14 Sep 2016, at 16:00, Robert Goldman <rpgoldman at> wrote:
> On 9/14/16 Sep 14 -6:14 AM, Faré wrote:
>> I don't know whether that would help on Windows, but I have a fix for
>> the require-system function that hopefully makes test-force stable, in
>> !16 on gitlab.
> Mostly I'm working my way back through history, then forward.
> was broken because of the typo.
> has the typo fixed, but fails test-clean-load on ecl_bytecodes.
> I believe that this is spurious, though.  It's crashing on the code
> that hooks into REQUIRE, and it crashes only when run as
> make test-clean-load l=ecl_bytecodes
> and NOT when run as
> -c ecl_bytecodes
> Here's the error:
> An error occurred during initialization:
> In form
>         (LOOP :FOR
>               PROVIDER
>               :IN
>               :COLLECT
>                               *WRAPPED-MODULE-PROVIDER*
>                               #'(LAMBDA (MODULE-NAME)
>                                   (WRAP-MODULE-PROVIDER PROVIDER
>                                                         MODULE-NAME))))))
> Wrong number of arguments passed to function NIL..
> I have checked what I thought was the obvious hypothesis: a NIL in
> *MODULE-PROVIDER-FUNCTIONS* -- but that is not the cause.  And why the
> intercession of "make" should matter, I cannot say.

I believe that was fixed by the commit immediately after, namely 33a2560f8589ae5b436f0fc26a75591cf2edcc60, no?

I could create a branch off of e.g. for your testing where I cherry-pick from the current master, throw out irrelevant merges and clean up the history a bit, to make things easier to bisect.


More information about the asdf-devel mailing list