Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-dev@incubator.apache.org
Message-ID: <766021660.1223914964431.JavaMail.jira@brutus>
Date: Mon, 13 Oct 2008 09:22:44 -0700 (PDT)
From: "Paul Carey (JIRA)" <jira@apache.org>
To: couchdb-dev@incubator.apache.org
Subject: [jira] Commented: (COUCHDB-135) Offset regression between 0.8.0 and
 trunk
In-Reply-To: <1188454600.1223665424258.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639090#action_12639090 ] 

Paul Carey commented on COUCHDB-135:
------------------------------------

The RelaxDB library contains a couple of hundred lines of pagination related test code - the majority of the tests rely on the correct offset being returned.

All these tests pass against 0.8.0, but some fail against trunk. An inconsistent number of tests fail against trunk. Typically 2, sometimes 3.

If you're interested in running these pagination tests against CouchDB, run the following 

git clone git://github.com/paulcarey/relaxdb.git && cd relaxdb && git checkout a8a2d496462ad
and then simply
spec spec/paginate_spec.rb

The following shows the result of inconsistent test failures.
http://friendpaste.com/RHKnkRpG

> Offset regression between 0.8.0 and trunk
> -----------------------------------------
>
>                 Key: COUCHDB-135
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-135
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.9
>         Environment: OSX 10.5
>            Reporter: Paul Carey
>         Attachments: view_offsets.js
>
>
> The offset returned for certain map queries differs between 0.8.0 and 0.9.0r702929.
> The attached test can be pasted into couch_tests.js. It passes in 0.8.0 and fails in 0.9.
> I believe the skip query param must be passed for this bug to be exhibited. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.