Re: cl-test-grid mailing list and ASDF testing

[Anton Vodonosov]

04.09.2013, 20:21, "Dave Cooper" <david....@genworks.com>:
> Hi Anton,
> О©╫First of all is there a working cl-test-grid mailing list these days, or did it get snuffed out when common-lisp.net got transferred to new box (we are working on getting that whole common-lisp.net situation straightened out).

Hello Dave,

Google group cl-test-grid is used as a mailing list (CC'ing here)

> Secondly, I got pulled into ASDF testing on the various CL platforms I keep installed
> over here and I want to get going on cl-test-grid again and get it running on my machines
> on an automated basis. I would like to integrate this ASDF testing with my cl-test-grid
> efforts if possible. О©╫I'm supposed to be testing the latest development head of ASDF.
>
> Right now ASDF comes with a Makefile which does all the tests, but it just puts the output
> into the asdf source tree. I would like to make some kind of toplevel thing on top of this
> which puts the results into folders with
>
> О©╫date/asdf-version/OS-identifier/CL-implementation-identifier/...results...
>
> My guess is that cl-test-grid already handles the labeling of test outputs like this to
> some extent, so I thought it would be best to integrate my ASDF testing with cl-test-grid,
> rather than trying to re-invent all that stuff.

It is very welcome if you run cl-test-gird, especially because you have Allegro.
I only have Allegro Express, with limited heap size and often expiring licence.

As for running the ASDF tests performed by Makefile, I've been thinking
since receiving your email yesterday but don't see yet
how to apply cl-test-grid (or its building blocks) to simplify your goal.

cl-test-grid collects results of performing (ql:quickload :each-library)
or running test suite of a library. In both cases it is a result of running
a single lisp process. I am not familiar with asdf tests, but it looks
like ASDF tests involve more - running some shell scripts and starting lisp
process many times.

cl-test-grid results are annoteted by (asdf:implemnetation-identifier),
wich corresponds to OS-identifier/CL-implementation-identifier;
by date and by quicklisp version.

There is another area where cl-test-grid can help for ASDF testing:
we can run cl-test-grid tests (building every library in Quicklisp + 67 testsuites)
with new ASDF version and compare results with old ASDF. Thus detecting
any regressions/improvements in CL world caused by new ASDF.

We did so when Fare have been doing large refactoring of ASDF, resulted
in release of ASDF3. This testing revealed some bugs in ASDF
and also detected the libraries relied on private or undocumented
ASDF features, broken when ASDF implementation changed.

Best regards,
- Anton

>
> Regards
>
> О©╫Dave
>
> --
> My Best,
>
> Dave Cooper, Genworks Support
> david....@genworks.com, dave.genworks.com(skype)
> USA: 248-327-3253(o), 1-248-330-2979(mobile)
> UK: 0191 645 1699