[
https://issues.apache.org/jira/browse/COUCHDB-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992844#comment-14992844
]
Jay Doane commented on COUCHDB-2871:
------------------------------------
It looks like the values in eunit.ini are being overridden by those in
default_eunit.ini, which is generated from this line:
https://github.com/apache/couchdb/blob/master/setup_eunit.template#L15
via these templates:
https://github.com/apache/couchdb/blob/master/rel/overlay/etc/default.ini#L35
https://github.com/apache/couchdb/blob/master/rel/overlay/etc/default.ini#L61
with the values:
https://github.com/apache/couchdb/blob/master/setup_eunit.template#L3-L4
> 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)
