[
https://issues.apache.org/jira/browse/COUCHDB-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992882#comment-14992882
]
Jay Doane commented on COUCHDB-2871:
------------------------------------
Also, without some serious refactoring, it turns out that you can't set [httpd]
port = 0 because several config tests rely on the canonical value. For example:
<code>
in function config_tests:'-should_ensure_in_defaults/2-fun-1-'/1
(test/config_tests.erl, line 299)
in call from config_tests:'-should_ensure_in_defaults/2-fun-3-'/0
(test/config_tests.erl, line 298)
**error:{assertEqual_failed,[{module,config_tests},
{line,299},
{expression,"config : get ( \"httpd\" , \"port\" )"},
{expected,"5986"},
{value,"0"}]}
</code>
> 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)
