> I've noticed some of that stuff going on in elephant-unstable and
> haven't been able to track it down yet. I'm surprised to hear it's in
> stable... Any hints as to what kind of data this is failing on?
Reproduce using test suite:
* load elephant-tests, set up backend tests (I was using the PM backend)
* run backend tests
* delete all fasls in src/elephant
* reload elephant system
* run backend tests
* should break now at INDEX-RESET (log attached)
Now if you abort this test run and start another, it works fine.
Leslie
debugger invoked on a ELEPHANT-DESERIALIZATION-ERROR in thread #<THREAD
"initial thread" {A725821}>:
Condition ELEPHANT-DESERIALIZATION-ERROR was signalled.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY-TRANSACTION] retry db-postmodern transaction
1: [ABORT-TRANSACTION] DB-POSTMODERN::ABORT-TRANSACTION
2: [RETEST ] Rerun the test
#<IT.BESE.FIVEAM::TEST-CASE INDEX-RESET {AF7D621}>
3: [IGNORE ] Signal an exceptional test failure and abort the test
#<IT.BESE.FIVEAM::TEST-CASE INDEX-RESET {AF7D621}>.
4: [EXPLAIN ] Ignore the rest of the tests and explain current
results
5: [ABORT ] Exit debugger, returning to top level.
(DESERIALIZE
#S(ELEPHANT-MEMUTIL:BUFFER-STREAM
:BUFFER #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #XB7F9F008 :TYPE (*
(SB-ALIEN:UNSIGNED
8))>
:SIZE 39
:POSITION 39
:LENGTH 163845)
#<POSTMODERN-STORE-CONTROLLER (POSTGRESQL 127.0.0.1 elepm postgres PORT
5433)>)
0] sb-debug:*debug-condition*
#<ELEPHANT-DESERIALIZATION-ERROR {BDF33F1}>
0] (elephant::deserialization-error-condition *)
#<UNBOUND-SLOT %OID {BDF3119}>
0] (describe *)
#<UNBOUND-SLOT %OID {BDF3119}>
is a UNBOUND-SLOT.
Its slot values are
(:NAME ELEPHANT::%OID :INSTANCE #<IDX-ONE-B oid:NIL> SB-KERNEL::NAME
ELEPHANT::%OID).
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
