http://ec2-174-129-63-37.compute-1.amazonaws.com/test/log/20100316T233422/ab...
Testing: test-force.script Armed Bear Common Lisp 0.18.1 Java 1.6.0_0 Sun Microsystems Inc. OpenJDK Client VM Low-level initialization completed in 1.985 seconds. Startup completed in 3.591 seconds.
Caught ERROR while processing --eval option "(load "test- force.script")": Failed to find asdf-abcl.lisp in /ebs/test/asdf/tmp/asdf-abcl.abcl. Using abcl , test-force.script failed
This looks like a failure in ABCL's make-pathname or merge-pathnames mechanism.
Mark, can you comment?
In run-tests.sh I currently use export ASDF_OUTPUT_TRANSLATIONS="${asdfdir}:${asdfdir}/tmp/fasls/$ (basename $command):"
the problem arises when running run-tests.sh from a web server.
would it controvert the purpose fo the tests to set it to a single directory which i know the web server process can use?
Not at all. Make the variable unmodified if it still exists.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The Constitution may not be perfect, but it's a lot better than what we've got!
On Mar 17, 2010, at 3:55 PM, ] wrote:
http://ec2-174-129-63-37.compute-1.amazonaws.com/test/log/20100316T233422/ab...
Testing: test-force.script Armed Bear Common Lisp 0.18.1 Java 1.6.0_0 Sun Microsystems Inc. OpenJDK Client VM Low-level initialization completed in 1.985 seconds. Startup completed in 3.591 seconds.
Caught ERROR while processing --eval option "(load "test- force.script")": Failed to find asdf-abcl.lisp in /ebs/test/asdf/tmp/asdf-abcl.abcl. Using abcl , test-force.script failed
This looks like a failure in ABCL's make-pathname or merge-pathnames mechanism.
Mark, can you comment?
abcl-0.18.1 is not going to work with ASDF2. You currently need to compile ABCL from a post svn r12551 commit. The necessary fixes have been backported to the upcoming (any day now) abcl-0.19 release.
The specific bug you are encountering involves abcl-0.18.1 not being able to handle the renaming of a FASL, as ASDF2 compiles to "asdf-tmp.XXX" and then renames to "asdf-<LISP_IMPLEMENTATION>.XXX". Rather embaressing for us, really, so [we fixed it fast][1]
[1]: http://trac.common-lisp.net/armedbear/changeset/12550
[…]
--
"A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
On 2010-03-17, at 16:04 , Mark Evenson wrote:
On Mar 17, 2010, at 3:55 PM, ] wrote:
http://ec2-174-129-63-37.compute-1.amazonaws.com/test/log/ 20100316T233422/abcl-output.txt
[...]
abcl-0.18.1 is not going to work with ASDF2. You currently need to compile ABCL from a post svn r12551 commit. The necessary fixes have been backported to the upcoming (any day now) abcl-0.19 release.
The specific bug you are encountering involves abcl-0.18.1 not being able to handle the renaming of a FASL, as ASDF2 compiles to "asdf-tmp.XXX" and then renames to "asdf-<LISP_IMPLEMENTATION>.XXX". Rather embaressing for us, really, so [we fixed it fast][1]
i'll wait for that. please advise when it happens.
On 3/17/10 4:15 PM, james anderson wrote: […]
The specific bug you are encountering involves abcl-0.18.1 not being able to handle the renaming of a FASL, as ASDF2 compiles to "asdf-tmp.XXX" and then renames to "asdf-<LISP_IMPLEMENTATION>.XXX". Rather embaressing for us, really, so [we fixed it fast][1]
i'll wait for that. please advise when it happens.
[ABCL-0.19.1 has been released][1] (there was no public announcement of ABCL-0.19.0).
[1]: http://common-lisp.net/project/armedbear/
-
Faré -
james anderson -
Mark Evenson