Re: Running Lisp tests

I think I found out. This command works:

java -jar dist/abcl.jar --eval '(require (quote asdf))' --eval
'(asdf:initialize-source-registry `(:source-registry (:directory
,*default-pathname-defaults*) :inherit-configuration))' --eval
'(asdf:test-system :abcl/test/ansi/compiled)'7

The difference? build.xml includes the --noinit argument. Which skips
loading my init file which loads Quicklisp.

Apparently, ABCL's tests depend on prove [1] and it has to be installed
manually, or found via Quicklisp.

[1] http://quickdocs.org/prove/


On Fri, 7 Jun 2019 at 14:33, Alessio Stalla <[email protected]> wrote:

> Thanks. Indeed, it does not find the system:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *$ java -jar dist/abcl.jar Armed Bear Common Lisp 1.6.0-devJava 1.8.0_171
> Oracle CorporationJava HotSpot(TM) 64-Bit Server VMLow-level initialization
> completed in 0.273 seconds.Startup completed in 1.399 seconds.Loading
> /home/alessio/.abclrc completed in 8.881 seconds.Type ":help" for a list of
> available commands.CL-USER(1): (asdf:find-system :abcl)#<THREAD
> "interpreter" {3DF12085}>: Debugger invoked on condition of type
> MISSING-COMPONENT  Component "abcl" not foundRestarts:  0: RETRY
>               Retry ASDF operation.  1: CLEAR-CONFIGURATION-AND-RETRY Retry
> ASDF operation after resetting the configuration.  2: TOP-LEVEL
>         Return to top level.[1] CL-USER(2):
> asdf:*central-registry*(#P"/home/alessio/quicklisp/quicklisp/")[1]
> CL-USER(3): (push #P"." asdf:*central-registry*)(#P"./"
> #P"/home/alessio/quicklisp/quicklisp/")[1] CL-USER(4):
> 0#<:ASDF/SYSTEM:SYSTEM "abcl">*
>
> Is this a bad interaction with Quicklisp? This is my .abclrc:
>
>
>
>
>
> *;;; The following lines added by ql:add-to-init-file:#-quicklisp(let
> ((quicklisp-init (merge-pathnames "quicklisp/setup.lisp"
> (user-homedir-pathname))))  (when (probe-file quicklisp-init)    (load
> quicklisp-init)))*
>
> Thanks,
> Alessio
>
> On Sat, 1 Jun 2019 at 02:12, Mark Evenson <[email protected]> wrote:
>
>>
>>
>> > On May 27, 2019, at 20:07, Alessio Stalla <[email protected]>
>> wrote:
>> >
>> > Greetings,
>> >
>> > I have trouble running ABCL's Lisp test suites:
>> >
>> > $ ant abcl.test
>> > ...lots of output...
>> >      [java] Caught :ASDF/FIND-COMPONENT:MISSING-DEPENDENCY while
>> processing --eval option "(asdf:test-system :abcl/test/ansi/compiled)":
>> >      [java]   #<MISSING-DEPENDENCY {1337E679}>
>> >      [java] Java Result: 2
>> > ...etc...
>> >
>> > Do you have any idea?
>>
>> What does (asdf:find-system :abcl) return?
>>
>> You need to have the [ANSI-TEST repository cloned locally][ansi-test] as
>> a sibling of where “abcl.asd” is located.  This is noted in the [comments
>> within “abcl.asd”][1], and we could certainly profit for a better message
>> in the signaled condition.
>>
>> TODO automate this as part of the things [ABCL-BUILD][abcl-build] can
>> install locally for the user.
>>
>> [ansi-test]: https://gitlab.common-lisp.net/ansi-test/ansi-test.git
>> [1]: https://abcl.org/trac/browser/trunk/abcl/abcl.asd#L86
>> [abcl-build]:
>> https://abcl.org/trac/browser/trunk/abcl/contrib/abcl-build/build
>>
>> --
>> "A screaming comes across the sky.  It has happened before but there is
>> nothing
>> to compare to it now."
>>
>>
>>
>>
>>
>>