[elephant-devel] elephant installation on sbcl 1.0.26.1

Fri Mar 13 01:03:15 UTC 2009

Great news!  I'm glad it works for you.

The tests are not guaranteed to be idempotent, although we work hard  
to make them so.  Try deleting the test db (the easy way is to use / 
tests/delscript.sh) and re-running; should work great from within  
slime now.

I'll add a ticket for the SLIME subprocess stream problems.

Cheers,
Ian

On Mar 12, 2009, at 4:47 PM, mosi wrote:

> Hi Ian,
>
> it works!
> This is a music to my ears:
> ---
> (do-backend-tests)
> ...
> Single store mode: ignoring.
> Did 500 checks.
>    Pass: 497 (99%)
>    Skip: 0 ( 0%)
>    Fail: 3 ( 0%)
>
> Failure Details:
> --------------------------------
> INDEXING-CHANGE-CLASS []:
>      1 evaluated to 1, which is not = to 2..
> --------------------------------
> --------------------------------
> INDEXING-BASIC []:
>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated
> to 4, which is not = to 2..
> --------------------------------
> --------------------------------
> INDEXING-BASIC []:
>      (LENGTH (GET-INSTANCES-BY-RANGE 'IDX-ONE-F 'SLOT1 N (+ 1 N)))
> evaluated to 5, which is not = to 3..
> --------------------------------
>
> That was slime environment.
> In the sbcl prompt, all 500 tests passed OK.
> I`m baffled as to why this might be.
>
> Thank you very much,
> let`s try some exciting stuff with elephant.
> Best regards,
> mosi
>
>
> 2009/3/12 Ian Eslick <eslick at media.mit.edu>:
>> A couple of quick points:
>>
>> - The latest elephant requires BDB 4.7
>>
>> - The C compilation step can cause problems when run from
>>   within slime, doing an initial compile from the console typically
>>   fixes this.
>>
>> - Sometimes SBCL complains the compile failed due to package export
>>   or other issues but things are fine.
>>
>> Do you have the trace of activity printed to the lisp repl window?
>> That is more informative than the backtrace.
>>
>> Thanks,
>> Ian
>>
>> On Mar 12, 2009, at 5:00 AM, mosi wrote:
>>
>>> Hi,
>>> i tried the following:
>>> This is SBCL 1.0.26.1 (threading on, unicode on) on debian linux,
>>> compiled from clbuild, run on SLIME 2008-12-23.
>>> I followed the installation instructions from
>>> http://common-lisp.net/project/elephant/doc/
>>>
>>> pulled the latest build:
>>> darcs get http://www.common-lisp.net/project/elephant/darcs/elephant-1.0
>>>
>>> installed all dependencies (lots of them were already installed
>>> previously by asdf-install: and clbuild), the berkeleydb 4.5 in the
>>> default folders, configured the my-config.sexp
>>>
>>> There are some problems during the compilation of elephant:
>>> memutils, serializer, serializer1, serializer2, unicode, etc.  
>>> succeed
>>> to compile, but throw: asdf-compile failed, and recompile does not
>>> help.
>>> -----------
>>> erred while invoking #<COMPILE-OP NIL {B62E909}> on
>>> #<CL-SOURCE-FILE "memutil" {BC60411}>
>>>  [Condition of type ASDF:COMPILE-FAILED]
>>>
>>> Restarts:
>>> 0: [TRY-RECOMPILING] Try recompiling memutil
>>> 1: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL {B62E909}> on
>>> #<ASDF:CL-SOURCE-FILE "memutil" {BC60411}>.
>>> 2: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {B62E909}> on
>>> #<ASDF:CL-SOURCE-FILE "memutil" {BC60411}> as having been  
>>> successful.
>>> 3: [RETRY] Retry SLIME REPL evaluation request.
>>> 4: [ABORT] Return to SLIME's top level.
>>> 5: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread"
>>> RUNNING {B7170D1}>)
>>>
>>> Backtrace:
>>> 0: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP
>>> ASDF:CL-SOURCE-FILE)) #<unavailable argument> #<unavailable  
>>> argument>
>>> #<ASDF:COMPILE-OP NIL {B62E909}> #<ASDF:CL-SOURCE-FILE "memutil"
>>> {BC60411}>)
>>>     Locals:
>>>       SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
>>>       SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
>>>       SB-DEBUG::ARG-2 = #<ASDF:COMPILE-OP NIL {B62E909}>
>>>       SB-DEBUG::ARG-3 = #<ASDF:CL-SOURCE-FILE "memutil" {BC60411}>
>>> 1: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0.
>>> SB-PCL::.ARG1.)) ..)
>>>     Locals:
>>>       SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
>>>       SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
>>>       SB-DEBUG::ARG-2 = #<ASDF:COMPILE-OP NIL {B62E909}>
>>>       SB-DEBUG::ARG-3 = #<ASDF:CL-SOURCE-FILE "memutil" {BC60411}>
>>> 2: ((SB-PCL::FAST-METHOD ASDF:PERFORM ASDF:AROUND (ASDF:COMPILE-OP
>>> ASDF:CL-SOURCE-FILE)) ..)
>>>     Locals:
>>>       SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
>>>       SB-DEBUG::ARG-1 = #S(SB-PCL::FAST-METHOD-CALL ..)
>>>       SB-DEBUG::ARG-2 = #<ASDF:COMPILE-OP NIL {B62E909}>
>>>       SB-DEBUG::ARG-3 = #<ASDF:CL-SOURCE-FILE "memutil" {BC60411}>
>>> 3: ((LAMBDA ()))
>>> 4: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))
>>> 5: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]477))
>>> 6: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK ..)
>>> 7: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA #) {BB53A6D}>)
>>> [:EXTERNAL]
>>> 8: (ASDF:OPERATE ASDF:LOAD-OP :ELEPHANT)[:EXTERNAL]
>>> 9: (SB-INT:SIMPLE-EVAL-IN-LEXENV (ASDF:OPERATE 'ASDF:LOAD-OP
>>> :ELEPHANT) #<NULL-LEXENV>)
>>> 10: (SWANK::EVAL-REGION "(asdf:operate 'asdf:load-op :elephant)\n")
>>> 11: ((LAMBDA ()))
>>> 12: (SWANK::TRACK-PACKAGE #<CLOSURE (LAMBDA #) {AF72AE5}>)
>>> 13: (SWANK::CALL-WITH-RETRY-RESTART "Retry SLIME REPL evaluation
>>> request." #<CLOSURE (LAMBDA #) {AF72A75}>)
>>> 14: (SWANK::CALL-WITH-BUFFER-SYNTAX NIL #<CLOSURE (LAMBDA #)
>>> {AF72A5D}>)
>>> 15: (SWANK::REPL-EVAL "(asdf:operate 'asdf:load-op :elephant)\n")
>>> 16: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL  
>>> "(asdf:operate
>>> 'asdf:load-op :elephant)\n") #<NULL-LEXENV>)
>>> 17: (SWANK::EVAL-FOR-EMACS (SWANK:LISTENER-EVAL "(asdf:operate
>>> 'asdf:load-op :elephant)\n") "COMMON-LISP-USER" 13)
>>> 18: (SWANK::PROCESS-REQUESTS NIL)
>>> 19: ((LAMBDA ()))
>>> 20: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION
>>> SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {B85D7AD}>)
>>> 21: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {B48E811}>
>>> #<CLOSURE (LAMBDA #) {B85D7BD}>)
>>> 22: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {B48E811}>
>>> #<CLOSURE (LAMBDA #) {B85D7AD}>)
>>> 23: (SWANK::HANDLE-REQUESTS #<SWANK::CONNECTION {B48E811}> NIL)
>>> ------------
>>> After accepting the compilation as successful, everything looks ok:
>>>
>>> ; caught WARNING:
>>> ;   These variables are undefined:
>>> ;     ELEPHANT::*NUMBER-RELATION-FUNCTIONS*
>>> ;     ELEPHANT::*STRING-RELATION-FUNCTIONS* ELEPHANT::FILTER-BY-
>>> RELATION
>>> ;     ELEPHANT::FILTER-INSTANCE
>>> ;
>>> ; compilation unit finished
>>> ;   caught 49 WARNING conditions
>>> ;   caught 2 STYLE-WARNING conditions
>>> ;   printed 805 notes
>>> NIL
>>> -----------
>>> after that, tried to test:
>>> (setf *test-db-spec* '(:BDB "/tmp/db/"))
>>> (open-store *test-db-spec*)
>>> -----------
>>> invalid number of arguments: 1
>>>  [Condition of type SB-INT:SIMPLE-PROGRAM-ERROR]
>>>
>>> Restarts:
>>> 0: [RETRY] Retry SLIME REPL evaluation request.
>>> 1: [ABORT] Return to SLIME's top level.
>>> 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread"
>>> RUNNING {B7170D1}>)
>>>
>>> Backtrace:
>>> 0: (DB-BDB::%DB-ENV-CREATE #<unavailable argument> #<unavailable
>>> argument>)[:EXTERNAL]
>>>     Locals:
>>>       SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
>>>       SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
>>>       SB-DEBUG::ARG-2 = :<NOT-AVAILABLE>
>>> 1: (DB-BDB::DB-ENV-CREATE)
>>>     [No Locals]
>>> 2: ((SB-PCL::FAST-METHOD ELEPHANT::OPEN-CONTROLLER
>>> (DB-BDB::BDB-STORE-CONTROLLER)) #<unavailable lambda list>) 
>>> [:EXTERNAL]
>>>     [No Locals]
>>> 3: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0.
>>> SB-INT:&MORE SB-PCL::.DFUN-MORE-CONTEXT. SB-PCL::.DFUN-MORE-COUNT.))
>>> ..)
>>> 4: (OPEN-STORE #<unavailable lambda list>)[:EXTERNAL]
>>> 5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (OPEN-STORE *TEST-DB-SPEC*) #<NULL-
>>> LEXENV>)
>>> ---------
>>> and:
>>> EL-TESTS> (do-backend-tests)
>>> the same error.
>>>
>>> I tried elephant 1.0 stable, 0.9, sbcl 23 with the latest elephant,
>>> but every time it gives another error, 0.9 crashes miserably,
>>> resulting in a memory overload.
>>>
>>> What are the exact prerequisities you use on a running system?
>>> Any idea what went wrong?
>>>
>>> Thanks a lot.
>>>
>>> /o>
>>> |/
>>>
>>> _______________________________________________
>>> elephant-devel site list
>>> elephant-devel at common-lisp.net
>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>
>>
>> _______________________________________________
>> elephant-devel site list
>> elephant-devel at common-lisp.net
>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel