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

Adam Kocoloski commented on COUCHDB-176:
----------------------------------------

Hi, I can reproduce this one.  It looks like db.deleteDb() is a no-op with 
Opera 0.62 (at least the DELETE operation never shows up in the log).  As a 
result db.createDb() results in a 409 every time.

Adam

> Test Suite fails to run
> -----------------------
>
>                 Key: COUCHDB-176
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-176
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 0.9
>         Environment: Apache CouchDB 0.9.0a725828-incubating compiled from SVN 
> on OS X 10.5.5, erlang 5.6.5, Opera 9.62
>            Reporter: Rob Crowther
>            Priority: Blocker
>
> Installed CouchDB trunk from SVN, (chmod|chown) -R couchdb 
> (/usr/local/etc/couchdb | /usr/local/var/lib/couchdb | 
> /usr/local/var/log/couchdb), ran couchdb as couchdb user (sudo -u couchdb 
> couchdb). Went to http://127.0.0.1:5984/_utils/index.html, clicked Test 
> Suite, clicked Run All, was presented with errors.
> The first test fails with
> basics        error   1248ms   
> Assertion failed: db.info().db_name == "test_suite_db"
> Assertion failed: db.info().doc_count == 0
> Assertion failed: db.info().doc_count == 4
> Exception raised: {"error":"conflict","reason":"Document update 
> conflict.","stacktrace":"n/a; see 'opera:config#UserPrefs|Exceptions Have 
> Stacktrace'\u0000"}
> All subsequent tests (until an apparent hang at view_collation) failed with 
> (e.g.):
> all_docs      error   16ms     
> Exception raised: {"error":"file_exists","reason":"The database could not be 
> created, the file already exists.","stacktrace":"n/a; see 
> 'opera:config#UserPrefs|Exceptions Have Stacktrace'\u0000"}

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

Reply via email to