[
https://issues.apache.org/jira/browse/COUCHDB-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802592#comment-15802592
]
ASF GitHub Bot commented on COUCHDB-3259:
-----------------------------------------
GitHub user eiri opened a pull request:
https://github.com/apache/couchdb-couch/pull/220
Fix couchdb_views tests
Previous commit made couch_file to monitor db_pid instead of linking to it,
so number of `monitored_by` for couch_db process, checked in
`couchdb_views_tests`, changed.
COUCHDB-3259
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-couch fix-views_tests
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-couch/pull/220.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #220
----
commit 7a5a1a9732abaaa47b90b090c17c72c161e0bad0
Author: Eric Avdey <[email protected]>
Date: 2017-01-05T21:30:00Z
Fix couchdb_views tests
Previous commit made couch_file to monitor db_pid
instead of linking ot it, so number of monitored_by
for couch_db process, checked in couchdb_views_tests,
changed.
COUCHDB-3259
----
> Don't trap exits in couch_file
> ------------------------------
>
> Key: COUCHDB-3259
> URL: https://issues.apache.org/jira/browse/COUCHDB-3259
> Project: CouchDB
> Issue Type: Bug
> Reporter: Robert Newson
> Fix For: 2.1.0
>
>
> It turns out to be impossible to trap the exit message from the parent
> process, which is the only reason couch_file traps exits in the first
> place (i.e, this has never worked).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
