couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (Updated) (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-1338) JS CLI test suite: have CouchDB start with port=0
Date Sun, 08 Jan 2012 05:34:39 GMT


Randall Leeds updated COUCHDB-1338:

    Attachment: v2-0002-Fix-JS-tests-for-COUCHDB-1338.patch
> JS CLI test suite: have CouchDB start with port=0 
> --------------------------------------------------
>                 Key: COUCHDB-1338
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Test Suite
>    Affects Versions: 1.3
>            Reporter: Jan Lehnardt
>            Assignee: Randall Leeds
>            Priority: Blocker
>             Fix For: 1.3
>         Attachments: v1-0001-COUCHDB-1338-run-js-tests-with-port-0.patch, v1-0002-Fix-JS-tests-for-COUCHDB-1338.patch,
v2-0001-COUCHDB-1338-run-js-tests-with-port-0.patch, v2-0002-Fix-JS-tests-for-COUCHDB-1338.patch
> The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB
using make dev && utils/run -b and stops it with utils/run -d.
> One issue with this is that one might have CouchDB already running on the default port
5984. The suggestion here is to start CouchDB with an additional .ini file that sets the port
number to 0 to let the TCP stack figure out a free port for us. The tests then need to be
updated to discover the automatic port using the couch.uri file.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message