[imp-hackers] Another topic: ANSI standard test suite

[Juan Jose Garcia-Ripoll]

On Mon, Jun 29, 2009 at 4:19 PM, Sam Steingold<sds at gnu.org> wrote:
> On Mon, Jun 29, 2009 at 8:15 AM, Juan Jose
> Garcia-Ripoll<juanjose.garciaripoll at googlemail.com> wrote:
>> On Fri, Jun 26, 2009 at 7:10 PM, Sam Steingold<sds at gnu.org> wrote:
>>> well, in general, I am very unhappy with the current infrastructure
>>> (basically, you cannot rerun a failing test in a fresh CL invocation
>>> without first loading the whole test suite, which can take a long
>>> time), so I would not mind ditching it in favor of something much
>>> simpler, along the lines of the clisp or sacla test suites.
>>
>> I do not have problems running individual test files. Tests do have
>> dependencies on commodity functions, such as those that implement
>> compiler test cases and the like. However, once you know this, it is
>> not difficult to just use a given set of tests. My script "run_this"
>> lives in the ansi/ tests suite directory and I can perfectly do
>> ./run-this compile-file and use it
>>
>> #!/bin/sh
>>
>> cat | ecl -norc <<EOF
>> (load "gclload1.lsp")
>
> this line takes forever - at least compared to copy/pasting a few lines.

Well, tests have dependencies on sets of data that are constructed by
the files from gclload1.lsp. I do not know how you are going to remove
those dependencies without making the tests extremely verbose by
constructing the data there. Besides, I really do not see such a time
loss

$ ecl -norc -eval '(time (load "gclload1.lsp"))'
[...]
 time : 4.356 secs
run time  : 0.860 secs
gc count  : 4 times
consed    : 21525824 bytes

And once gclload1.lsp is loaded, you can run as many tests as you want
and do as much copy pasting as you wish.

Juanjo


-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com