clisp testing on linux
fahree at gmail.com
Wed Dec 19 01:36:50 UTC 2018
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.
The allowed keywords are NIL
That's weird, because I've been using these arguments to copy-file
since the very first ASDF 3 prerelease (2.27) in 2013 and never had
this issue before. I'll blame the NixOS build script for failing to
configure clisp properly.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
A cuddle a day keeps the shrink away
On Tue, Dec 18, 2018 at 6:49 PM Robert Goldman <rpgoldman at sift.info> wrote:
> 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?
> On 18 Dec 2018, at 17:43, Faré wrote:
> 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 18.09.1228.a4c4cbb613c, I instead get:
> TEST ABORTED:
> POSIX:COPY-FILE: illegal keyword/value pair :METHOD, :RENAME in argument list.
> The allowed keywords are NIL
> This suggests that uiop/filesystem:rename-file-overwriting-target has
> bitrotten on the latest CLISP. Any volunteer to fix that in a
> backward-compatible way? I'll pass.
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
> We must do away with all newspapers. A revolution cannot be accomplished
> with freedom of the press. — Ernesto "Che" Guevara
> On Tue, Dec 18, 2018 at 3:58 PM Robert Goldman rpgoldman at sift.info wrote:
> 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 about this, but thought I would ask for suggestions:
> Test TEST-FILE-ENCODING-U8: should be UTF-8
> ; Registering system test-file-encoding-u8
> *** - handle_fault error2 ! address = 0x55f6cc8871d0 not in [0x55db332bd000,0x55db336926d8) !
> SIGSEGV cannot be cured. Fault address = 0x55f6cc8871d0.
> GC count: 203
> Space collected by GC: 304757408
> Run time: 3 915662
> Real time: 4 586182
> GC time: 0 693431
> Permanently allocated: 165368 bytes.
> Currently in use: 8753400 bytes.
> Free space: 1903262 bytes.
> Segmentation fault (core dumped)
> Using clisp, test-encodings.script failed
More information about the asdf-devel