[
https://issues.apache.org/jira/browse/COUCHDB-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491134#comment-14491134
]
Alexander Shorin commented on COUCHDB-2659:
-------------------------------------------
The reason why they (errors) happened is that in 313 PR dev/run now ensures
that all system databases: _users, _replicator, _metadata are created.
Previously, they were not available for developers cluster.
If I drop _metadata database, PouchDB test suite for couchdb-master bypasses
these failures. This could be a workaround for PouchDB, but certainly, we found
a bug for CouchDB as I can see.
> CouchDB master failing the PouchDB test suite - live changes
> ------------------------------------------------------------
>
> Key: COUCHDB-2659
> URL: https://issues.apache.org/jira/browse/COUCHDB-2659
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Database Core
> Reporter: Nolan Lawson
>
> See [this comment |
> https://github.com/pouchdb/pouchdb/pull/3722#issuecomment-91571425] for
> details. We have automated tests that pull in the latest CouchDB master
> branch and run the PouchDB test suite against it, and recently our tests
> started failing due to [apache/couchdb#313 |
> https://github.com/apache/couchdb/pull/313]. So I switched back to admin
> party mode, but now it's failing for another reason:
> {quote}
> 1) test.attachments.js-http #3074 live changes():
> Uncaught Database encountered an unknown error
> {quote}
> Instructions for running the PouchDB test suite are in our TESTING.md, it's
> pretty straightforward but basically you just want to point it to any CouchDB
> server like so and run the tests:
> {code}
> BAIL=0 COUCH_HOST=http://localhost:15984 npm test
> {code}
> {{BAIL=0}} will prevent bailing upon the first error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
