The latest tweak was followed by a Jenkins (linux) test failure for
clisp on `test-encodings.script`, with a segmentation fault.
I cannot reliably replicate this, and I don't see any reason to assume
that this is ASDF's fault, rather than clisp's.
I'm not sure that there is anything I can do
Yes, I am on Linux amd64 using
make -f Makefile t l=clisp t=test-encodings.script
On Debian, using GNU CLISP 2.49.92 (2018-02-18) everything works fine.
On NixOS, using GNU CLISP 2.49.60+ (2017-06-25) I get the error
POSIX:COPY-FILE: illegal keyword/value pair :METHOD, :RENAME in argument list.
On Tue, Dec 4, 2018 at 9:21 PM Hugo Ishimaru wrote:
> I have made an extension of package-inferred-system that interprets
> star `*' and globstar `**' in a package name, which I will use in the
> future for my library.
> https://github.com/privet-kitty/wild-package-inferred-system
> (My
Are you getting that error on the same test (`test-encodings.script`),
or is it in a different test script?
It would be interesting if it's on the same test, because I am *not*
seeing this error, and maybe it's causing the segmentation fault. Would
you post the context of the error?
Well, CLISP is known for its deterministic but chaotic segfaults (i.e.
sensitive to the slightest perturbation in input), probably due to
some GC bug somewhere, which would explain your failure.
Interestingly, I experience a different failure using GNU CLISP
2.49.60+ (2017-06-25) on NixOS
