<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">Are you getting that error on the same test (<code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">test-encodings.script</code>), or is it in a different test script?</p>
<p dir="auto">It would be interesting if it's on the same test, because I am <em>not</em> seeing this error, and maybe it's causing the segmentation fault. Would you post the context of the error?</p>
<p dir="auto">Thanks!<br>
R</p>
<p dir="auto">On 18 Dec 2018, at 17:43, Faré wrote:</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<p dir="auto">Well, CLISP is known for its deterministic but chaotic segfaults (i.e.<br>
sensitive to the slightest perturbation in input), probably due to<br>
some GC bug somewhere, which would explain your failure.</p>
<p dir="auto">Interestingly, I experience a different failure using GNU CLISP<br>
2.49.60+ (2017-06-25) on NixOS 18.09.1228.a4c4cbb613c, I instead get:<br>
TEST ABORTED:<br>
POSIX:COPY-FILE: illegal keyword/value pair :METHOD, :RENAME in argument list.<br>
The allowed keywords are NIL</p>
<p dir="auto">This suggests that uiop/filesystem:rename-file-overwriting-target has<br>
bitrotten on the latest CLISP. Any volunteer to fix that in a<br>
backward-compatible way? I'll pass.</p>
<p dir="auto">—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•<br>
<a href="http://fare.tunes.org" style="color:#777">http://fare.tunes.org</a><br>
We must do away with all newspapers. A revolution cannot be accomplished<br>
with freedom of the press. — Ernesto "Che" Guevara</p>
<p dir="auto">On Tue, Dec 18, 2018 at 3:58 PM Robert Goldman <a href="mailto:rpgoldman@sift.info" style="color:#777">rpgoldman@sift.info</a> wrote:</p>
<blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999">
<p dir="auto">The latest tweak was followed by a Jenkins (linux) test failure for clisp on test-encodings.script, with a segmentation fault.</p>
<p dir="auto">I cannot reliably replicate this, and I don't see any reason to assume that this is ASDF's fault, rather than clisp's.</p>
<p dir="auto">I'm not sure that there is anything I can do about this, but thought I would ask for suggestions:</p>
<p dir="auto">Test TEST-FILE-ENCODING-U8: should be UTF-8<br>
; Registering system test-file-encoding-u8</p>
<p dir="auto">*** - handle_fault error2 ! address = 0x55f6cc8871d0 not in [0x55db332bd000,0x55db336926d8) !<br>
SIGSEGV cannot be cured. Fault address = 0x55f6cc8871d0.<br>
GC count: 203<br>
Space collected by GC: 304757408<br>
Run time: 3 915662<br>
Real time: 4 586182<br>
GC time: 0 693431<br>
Permanently allocated: 165368 bytes.<br>
Currently in use: 8753400 bytes.<br>
Free space: 1903262 bytes.<br>
Segmentation fault (core dumped)<br>
Using clisp, test-encodings.script failed</p>
</blockquote>
</blockquote>
</div>
</div>
</body>
</html>