trying some ASDF tests on Windows (was: Re: [asdf-devel] Volunteer for LispWorks testing?)
Hi Robert,
[also cc'ing this to asdf-devel in case anyone else has feedback]
Ok, shifting gears a little bit here first...
I'm trying a few test runs of the ASDF test suite on Windows. Platforms on Windows which I have available to test right now are: Allegro CL (several variations), and CCL.
To prepare to run the tests on Windows, I installed cygwin and cygwin's make. Then to run the tests, I do (for lack of having this more automated so far):
1. set ASDF_TEST_LISPS appropriately.
2. Edit run-tests.sh to point to appropriate Lisp executables.
3 Invoke "make test-all-no-upgrade" from the cygwin command shell.
Let's try CCL first. Here are the outputs:
https://www.dropbox.com/sh/jc2cqwpkp06dupm/-vvd5gFwTk/cl/tests/asdf/output/2...
Summary: 42 out of 47 pass (5 failures).
I can try to dive into these further, but I thought I would post the results here first in case anything is obvious to anyone.
Incidentally, I have been running ASDF in production with Allegro CL for some time now (including asdf:monolithic-fasl-op) and it has been working well. There are some startup glitches for running ASDF tests on Windows/Allegro right now. After the CCL issue is resolved I will return to trying to get the tests to run for Allegro on Windows.
Regards,
Dave
P.S. I can see the Launchpad link you sent earlier.
On Tue, Sep 3, 2013 at 8:41 PM, Robert P. Goldman rpgoldman@sift.infowrote:
Dave Cooper wrote:
In the meantime do you think it's worth me diving into what is apparently this one test failure on LWM?
That would be great, thanks!
If there is anything I can do to help you get acclimated and figure it out, let me know. I haven't had a chance to look into it yet. I've been on vacation and now I'm in the thick of things at work.
I will try to put some notes in the ASDF ticket on launchpad. Can you see that? If not, please let me know.
Best, Robert
Dave Cooper wrote:
Hi Robert,
[also cc'ing this to asdf-devel in case anyone else has feedback]
Ok, shifting gears a little bit here first...
I'm trying a few test runs of the ASDF test suite on Windows. Platforms on Windows which I have available to test right now are: Allegro CL (several variations), and CCL.
To prepare to run the tests on Windows, I installed cygwin and cygwin's make. Then to run the tests, I do (for lack of having this more automated so far):
set ASDF_TEST_LISPS appropriately.
Edit run-tests.sh to point to appropriate Lisp executables.
You actually shouldn't need to do that -- there is one environment variable for each of the executables, and you can set those, if the default values don't work for you.
3 Invoke "make test-all-no-upgrade" from the cygwin command shell.
Let's try CCL first. Here are the outputs:
https://www.dropbox.com/sh/jc2cqwpkp06dupm/-vvd5gFwTk/cl/tests/asdf/output/2...
Summary: 42 out of 47 pass (5 failures).
I can try to dive into these further, but I thought I would post the results here first in case anything is obvious to anyone.
Incidentally, I have been running ASDF in production with Allegro CL for some time now (including asdf:monolithic-fasl-op) and it has been working well. There are some startup glitches for running ASDF tests on Windows/Allegro right now. After the CCL issue is resolved I will return to trying to get the tests to run for Allegro on Windows.
That would be great.
By the way, the bundle tests aren't working for me on a couple of other lisps.
cheers, r
On Wed, Sep 4, 2013 at 3:45 PM, Dave Cooper david.cooper@genworks.com wrote:
I'm trying a few test runs of the ASDF test suite on Windows. Platforms on Windows which I have available to test right now are: Allegro CL (several variations), and CCL.
To prepare to run the tests on Windows, I installed cygwin and cygwin's make. Then to run the tests, I do (for lack of having this more automated so far):
set ASDF_TEST_LISPS appropriately.
Edit run-tests.sh to point to appropriate Lisp executables.
Can't you just set (and export) the CCL variable? (And for Allegro, ALLEGRO and ALLEGROMODERN ?)
3 Invoke "make test-all-no-upgrade" from the cygwin command shell.
Let's try CCL first. Here are the outputs:
https://www.dropbox.com/sh/jc2cqwpkp06dupm/-vvd5gFwTk/cl/tests/asdf/output/2...
Summary: 42 out of 47 pass (5 failures).
I can try to dive into these further, but I thought I would post the results here first in case anything is obvious to anyone.
The test-bundle.script output suggests that, on Windows, there might be a bug in ccl:fasl-concatenate. Please create a reduced test, and open a bug against CCL if that is indeed the case, using http://trac.clozure.com/ccl/newticket
The test-configuration.script failure shows that some tests assume unix pathnames and : as separator between paths while parsing lists of pathnames in a string. On Windows, ; is the separator between paths. The tests need to be conditionalized on #+asdf-unix, and/or some non-unix equivalent has to be provided and/or the strings should be joined using (uiop:inter-directory-separator) rather than #: . Same failure in test-utilities.script.
The test-multiple.script failure reveals an error in run-program, that looks like it does a (cons "cmd" argument) instead of a (list "cmd" argument). Same failure in test-run-program.script.
NB: I am NOT going to fix these failures, though I apologize for introducing them. However, I am glad to be of help to anyone willing to figure out where and how to fix them.
Regards,
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org You think war is economically beneficial? Then why share those benefits with dirty foreigners? Let's have a civil war — A war we're sure to win!
-
Dave Cooper -
Faré -
Robert P. Goldman