Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Wed, 25 Jan 2012 17:46:40 +0000 (UTC)
From: "Paul Joseph Davis (Commented) (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1198854389.77054.1327513600235.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1086675294.75872.1327475621553.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COUCHDB-1390) Fix auth_cache etap test
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Paul Joseph Davis commented on COUCHDB-1390:
--------------------------------------------

Hrm. That's odd as it was deterministically failing for me. I'll try and reproduce this outside of the patches for COUCHDB-1391 which is where I discovered it. I thought I'd tracked it down to something specific but perhaps my updates changed something subtle. Will know more in a few minutes.
                
> Fix auth_cache etap test
> ------------------------
>
>                 Key: COUCHDB-1390
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1390
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: Paul Joseph Davis
>         Attachments: COUCHDB-1390.patch
>
>
> The auth_cache etap tests were failing for me. Debugged this to make sure it wasn't related to something else. Commit message is:
>     Fix for the auth_cache etap
>     
>     As it turns out, opening a doc by id is different than opening it using
>     a #doc_info record due to the inclusion of the full revision path. This
>     ended up breaking the auth_cache tests. This way includes the entire
>     revision path for all docs and not just first doc loads.
> Patching attaching in a few moments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira