couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Goodall <matt.good...@gmail.com>
Subject Re: 0.9 final sprint
Date Mon, 16 Mar 2009 16:53:22 GMT
2009/3/16 Matt Goodall <matt.goodall@gmail.com>:
> 2009/3/16 Chris Anderson <jchris@apache.org>:
>> On Mon, Mar 16, 2009 at 6:07 AM, Jan Lehnardt <jan@apache.org> wrote:
>>>
>>> On 15 Mar 2009, at 21:58, Chris Anderson wrote:
>>>
>>>> We are within striking distance of 0.9
>>>>
>>>> 12 Outstanding issues:
>>>>
>>>>
>>>> https://issues.apache.org:443/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310780&priority=1&status=1&status=4&fixfor=12313208&sorter/field=issuekey&sorter/order=DESC
>>>>
>>>> I think it'd be very cool if we could release in time for ApacheCon EU
>>>> - starts on March 23rd. I think this is feasible but it will require
>>>> some doing.
>>>>
>>>> Some of these tickets may be as simple as documentation or exploration
>>>> to see if the issue is resolved by the new replication security patch.
>>>> None of them look very challenging.
>>>
>>>
>>> I see the replication test failing in Firefox and Safari 3.0 (but not Safari
>>> 4 beta)
>>>
>>> The test fails with
>>>
>>> {"error":"normal","reason":"{gen_server,call,[<0.29400.0>,get_result,infinity]}
>>>
>>> which comes as
>>>
>>> [info] [<0.29281.0>] 127.0.0.1 - - 'GET'
>>> /test_suite_db_a/_local%2Fb1fc9bd58a179f7aeb55e42d710fdceb 200
>>> [info] [<0.29359.0>] starting replication "b1fc9bd58a179f7aeb55e42d710fdceb"
>>> at <0.29400.0>
>>> [info] [<0.29400.0>] recording a checkpoint at source update_seq 20
>>> [error] [<0.29359.0>] Uncaught error in HTTP request: {exit,
>>>                                 {normal,
>>>                                  {gen_server,call,
>>>                                   [<0.29400.0>,get_result,infinity]}}}
>>>
>>> in the CouchDB log
>>>
>>
>> I get this intermittently on my FF also. Running it a few times makes
>> it pass. I think this is more a problem with the test suite than with
>> replication. Can you make this a ticket? I think it'll be a fair
>> amount of work.
>
> I've seen the same, or very similar, error when triggering a
> replication using curl and Futon's replication page. I don't have any
> logs right now though.

Just happened again. I have no better logs to add to the above.

However, it does seem to be totally repeatable when replicating an
empty source database, and mostly repeatable when replicating a
database with no changes. In fact, if I add a new document to the
source database between replication attempts I cannot make it fail.

It doesn't seem to matter if the target database has changed.

Hope that helps!

- Matt

Mime
View raw message