On Nov 11, 2011, at 03:20 , Randall Leeds wrote:
> Can someone turn this into a ticket?
Good call, thanks for the nudge.
> Sounds like we need port=0 and a trap command.
I made one for each:
https://issues.apache.org/jira/browse/COUCHDB-1338
https://issues.apache.org/jira/browse/COUCHDB-1339
> Also, I noticed that running the tests directly seems to start/stop
> the server but make check doesn't? Is that correct?
`make check` now runs the JS cli tests as well, but I think you mean
the etap tests. There, you are correct, as individual tests will
start CouchDB as they need it. Most tests just test individual modules
and don't even launch a fully fledged CouchDB instance. The JS tests all
need a running instance, hence the difference.
Cheers
Jan
--
>
> On Mon, Oct 31, 2011 at 11:16, Noah Slater <[email protected]> wrote:
>> On Mon, Oct 31, 2011 at 2:38 PM, Paul Davis
>> <[email protected]>wrote:
>>
>> Before I forget, there's also a nifty trap command thing in case its
>>> killed by a signal. There's an example of its use here:
>>>
>>>
>>> https://svn.apache.org/repos/infra/infrastructure/trunk/projects/git/bin/update-mirror.sh
>>>
>>> Not sure how portable that is, but it seems like something we might
>>> want to look into to be extra sure that the node comes down.
>>>
>>
>> +1
>>
>> The trap command should be quite portable.
>>
