>> Maybe it's an artefact of SBCL using too much memory *while compiling*
>> and would go away if you used e.g. POIU to compile inside forks.
>
> How?
>
"Just" load POIU right after you load ASDF, and before you load anything else.
https://gitlab.common-lisp.net/qitab/poiu
> The test order is alph
02.03.2018, 05:33, "Faré" :
>>> Often failures in cl-test-grid are "just" the result of using too
>>> little memory,
>>
>> not little memory, but SBCL's conservative (i.e. imprecise) garbage
>> collection - it doesn't always recognize that an object is a garbage.
>>
>> I saw cases where CCL
On 1 Mar 2018, at 20:33, Faré wrote:
> PS: The newer test results look good. I'd like to see the results with
> the syntax-control branch, though. There also are a few minor bug
> fixes in the pipe that mean we'll have to re-test before release,
> anyway.
Concur...
>> Often failures in cl-test-grid are "just" the result of using too
>> little memory,
>
> not little memory, but SBCL's conservative (i.e. imprecise) garbage
> collection - it doesn't always recognize that an object is a garbage.
>
> I saw cases where CCL compiles a project under a 100MB heap,
> w
I updated the report with the rest of the results. The lisps tested:
abcl-1.5.0-fasl43-linux-x86
acl-10.0-linux-x86
acl-10.0m-linux-x86
acl-10.0ms-linux-x86
acl-10.0s-linux-x86
ccl-1.10-r16196-f96-linux-x86
ccl-1.11-r16635-f96-linux-x86
ccl-1.9-r15756-f96-linux-x86
clisp-2.49-unix-x86
ecl-16.1.2-u
16.02.2018, 22:02, "Faré" :
>
> Often failures in cl-test-grid are "just" the result of using too
> little memory,
not little memory, but SBCL's conservative (i.e. imprecise) garbage
collection - it doesn't always recognize that an object is a garbage.
I saw cases where CCL compiles a project
MR sent. I took the approach of setting the source-file. The etypecase
approach would have either introduced a circular dependency between
system.lisp and package-inferred-system.lisp or would have required
the package-inferred-system symbol to be exported from system.lisp
which felt wrong.
-Eric
