Ian, luckily I am in the development stages of my app, so I can freely
throw away my data whenever I like (it is just syslog data from some
very chatty networking hardware, so there is always more to be had). I
have experienced these issues on 32 and 64 bit systems, though my main
system is 6
This is very odd behavior. I have a live webapp that uses all this
stuff pretty heavily.
I did see this active cursor message earlier, but it was due to some
debugging churn in the BDB transaction handler a day or two ago.
Those issues should all be resolved now, but it's possible somethin
Unfortunately, things remain as before. Here is some additional debug
output that I found in the *inferior-lisp* buffer of my emacs session:
Deserialization error in map: returning nil for element
transaction has active cursors
PANIC: Invalid argument
PANIC: DB_RUNRECOVERY: Fatal error, run data
Thanks, Ian. All tests pass for me as well. I am running my
application with the new code and will let you know how it goes.
Thanks again!
Kevin
Ian Eslick wrote:
> I just checked in a few more fixes a few minutes ago. I finally was
> able to reproduce some of this locally. Try cleaning ou
I just checked in a few more fixes a few minutes ago. I finally was
able to reproduce some of this locally. Try cleaning out the test
database and re-running the tests. Everything passes for me on a
fresh DB and my own application is running fine too.
Ian
On Jan 10, 2009, at 2:04 PM, Kev
After pulling the latest patches and rebuilding without optimizations as
you suggest, I get the following errors, the second of which is slightly
different than what I was receiving previously.
First, a deserialization error:
Condition ELEPHANT-TYPE-DESERIALIZATION-ERROR was signalled.
[Cond
Sounds like there is prior state in the db. Try running delscript.sh
in the tests directory to clear out all the prior state.
I'll check in some further fixed tomorrow that may address the prior
problem you had.
Sent from my iPhone
On Jan 9, 2009, at 12:45 PM, Kevin Raison wrote:
> Ian, I
Ian, I pulled all new patches from darcs and did a rebuild as you
suggested. BDB test are now failing:
Did 491 checks.
Pass: 483 (98%)
Skip: 0 ( 0%)
Fail: 8 ( 1%)
Failure Details:
INDEXING-CHANGE-CLASS []:
1 evaluated to 1, which i
Hi Kevin,
I have some theories, but no conclusion yet. I did revert two very
small changes which could have been responsible. Please rebuild and
see if you can reproduce.
Thank you,
Ian
On Jan 7, 2009, at 9:10 PM, Kevin Raison wrote:
> I was finally able to recreate this in the repl (as o
Also try pushing :elephant-without-optimize onto *features* prior to
doing a force rebuild of elephant. This should give you some more
information and rule out any optimization/declaration related bugs.
Thank you,
Ian
On Jan 7, 2009, at 9:10 PM, Kevin Raison wrote:
> I was finally able to
The berkeleydb tests pass 100%.
Ian Eslick wrote:
> PS - Does the test suite pass on your system?
>
> On Jan 7, 2009, at 8:09 PM, Kevin Raison wrote:
>
>> I am seeing an intermittent error with 1.0 alpha when trying to
>> write to
>> an indexed btree (using BerkeleyDB 4.7 as provided by Ubunt
I am seeing this issue with both the alpha tag and the latest head.
Ian Eslick wrote:
> Sorry, this indicate a fresh DB. Which version of 1.0 are you using -
> the alpha tag or the latest head?
>
> Sent from my iPhone
>
> On Jan 7, 2009, at 9:35 PM, Kevin Raison wrote:
>
>> I apologize for
Sorry, this indicate a fresh DB. Which version of 1.0 are you using -
the alpha tag or the latest head?
Sent from my iPhone
On Jan 7, 2009, at 9:35 PM, Kevin Raison wrote:
> I apologize for replying to my own reply, but in the process of
> recreating this from a fresh bdb, i noticed another
Hi Kevin,
Thank you for the report; that's very odd behavior and I haven't seen
that locally. I'll look into this tonight. Are you using a fresh
repository or an pre-existing one that you upgraded to 1.0?
Ian
On Jan 7, 2009, at 9:35 PM, Kevin Raison wrote:
> I apologize for replying to my
PS - Does the test suite pass on your system?
On Jan 7, 2009, at 8:09 PM, Kevin Raison wrote:
> I am seeing an intermittent error with 1.0 alpha when trying to
> write to
> an indexed btree (using BerkeleyDB 4.7 as provided by Ubuntu's
> package
> repositories):
>
> The slot DB-BDB::INDICES-
I apologize for replying to my own reply, but in the process of
recreating this from a fresh bdb, i noticed another artifact of the
error condition. Before the unbound slot errors begin to appear, I get
an ELEPHANT:ELEPHANT-TYPE-DESERIALIZATION-ERROR; just once, and then
the unbound slot erro
I was finally able to recreate this in the repl (as opposed to seeing it
in my error logs), so here is a trace:
The slot DB-BDB::INDICES-CACHE is unbound in the object
#.
[Condition of type UNBOUND-SLOT]
Backtrace:
0: ((SB-PCL::FAST-METHOD SLOT-UNBOUND (T T T)) # # #
# DB-BDB::INDICES-C
17 matches
Mail list logo
