You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Jay Doane (JIRA)" <ji...@apache.org> on 2015/11/06 07:56:27 UTC

[jira] [Closed] (COUCHDB-2871) It should be possible to run "make eunit" while a dev cluster is running

     [ https://issues.apache.org/jira/browse/COUCHDB-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Doane closed COUCHDB-2871.
------------------------------
    Resolution: Not A Problem

Turns out this is not actually a problem for couchdb. Sorry for the waste of time!

> It should be possible to run "make eunit" while a dev cluster is running
> ------------------------------------------------------------------------
>
>                 Key: COUCHDB-2871
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2871
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Test Suite
>            Reporter: Jay Doane
>
> The default ports for eunit tests are:
> {cluster_port, 5984}
> {backend_port, 5986}
> as seen in https://github.com/apache/couchdb/blob/master/setup_eunit.template#L3-L4
> Unfortunately, the dev cluster runs haproxy on port 5984, so it's not possible to run the eunit tests while a dev cluster is running, which is inconvenient. Also unfortunate is that several tests in the config and couch applications rely on the backend_port being 5986.
> The good news is that we can change the eunit cluster_port from the default (to, e.g. 59840), but leave the backend_port as is, and enjoy the ability to run tests while a dev cluster is running.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)