On Mon, 2008-03-17 at 13:24 -0400, Ian Eslick wrote:
> I noticed this too but haven't had a chance to track it down. I don't
> see it on my local branch so I can check which patches went into head
> that aren't in unstable. I should probably do an import and integrate
> once I get my branch
On Mon, 2008-03-17 at 17:21 +0100, Leslie P. Polzer wrote:
> Hi Robert,
>
> > Furthermore, in attempt to solve this problem, I restored my local copy
> > to the head of the main repository, and am green only under BDB.
>
> I checked out a pristine copy and tried the BDB and PG tests, which al
I noticed this too but haven't had a chance to track it down. I don't
see it on my local branch so I can check which patches went into head
that aren't in unstable. I should probably do an import and integrate
once I get my branch clean.
Cheers,
Ian
On Mar 17, 2008, at 1:18 PM, Leslie P
> So, unfortunately, Leslie, I cannot re-apply our patch. If you have
> working code, please compute another patch directly against the CURRENT
> tip of the main development branch in the repository. I will then apply
> this and see if I can get to green.
Here's the updated and rebased ver
Hi Robert,
> Furthermore, in attempt to solve this problem, I restored my local copy
> to the head of the main repository, and am green only under BDB.
I checked out a pristine copy and tried the BDB and PG tests, which all
ran fine for me (after putting the concurrency tests into a differe
Dear Robert,
> I can see now that I did not apply Leslie's updated patch. I attempted
> to rollback and reapply the correct patch. Unfortunately, I was unable
> to get to a "green" state under any system. I find darcs much harder to
> work with than CVS (however, I had a great deal of ex
Thank you. That's good to knowpossibly all the confusion is in the
postmodern stuff.
On Sun, 2008-03-16 at 16:03 -0400, Ian Eslick wrote:
> I pulled a fresh copy of the current head and I found one issue:
>
> Mac OS X / Allegro / BDB 4.5 - no probs
> Mac OS X / Allegro / CLSQL - map-index-
I pulled a fresh copy of the current head and I found one issue:
Mac OS X / Allegro / BDB 4.5 - no probs
Mac OS X / Allegro / CLSQL - map-index-remove failed
Mac OS X / SBCL / BDB 4.5 - no probs
Mac OS X / SBCL / CLSQL - no probs
(I don't have a postgres test db setup at the moment)
Ian
On Mar
We should definitely find out what, if anything, is keeping the
current head from being green. However, the changes in the unstable
branch are so extensive, that our time prepping for the release are
better spent on identifying presents in that one (FYI - I only have
one or two failing tes
Dear Leslie and Ian Alex and Henrik,
I can see now that I did not apply Leslie's updated patch. I attempted
to rollback and reapply the correct patch. Unfortunately, I was unable
to get to a "green" state under any system. I find darcs much harder to
work with than CVS (however, I had a
Dear Robert,
I posted an updated version of the patch shortly after, and it seems
you applied the obsolete one. Can you check?
> I did personally have some problems...perhaps because Bordeaux Threads
> is not claiming to work on x86_64 architectures, darn it!
Hrm, I guess it should just
Dear Leslie,
Thanks for this patch. I have applied it to the main repository. I
hope you can work with Alex in the future to avoid any confusion, but in
any case I greatly appreciate the time you put into this.
I did personally have some problems...perhaps because Bordeaux Thread
On Fri, Mar 7, 2008 at 10:08 PM, Leslie P. Polzer <[EMAIL PROTECTED]> wrote:
>
> Yes, this works as it should.
> The problem is that the concurrency tests shouldn't be included
> in the standard backend test suite which gets run by
> DO-BACKEND-TESTS.
I think it just is a matter of putting this
Dear Henrik,
> 2008/3/7 Leslie P. Polzer <[EMAIL PROTECTED]>:
>>
>> Amendments:
>>
>> * handle pg error 23505 (duplicate primary key race condition)
>> * some notes on handled errors
>> * removed dbpm-error condition
>
> Does these fix the problems you reported earlier?
I believe this fixes
2008/3/7 Leslie P. Polzer <[EMAIL PROTECTED]>:
>
> Amendments:
>
> * handle pg error 23505 (duplicate primary key race condition)
> * some notes on handled errors
> * removed dbpm-error condition
Does these fix the problems you reported earlier?
Since Alex Mizrai is updating the postmodern cod
15 matches
Mail list logo
