[GitHub] jaydoane opened a new pull request #492: Test changes_listener dies on mem3_shards shutdown

[gi...@git.apache.org]

jaydoane opened a new pull request #492: Test changes_listener dies on mem3_shards shutdown
URL: https://github.com/apache/couchdb/pull/492
 
 
   <!-- Thank you for your contribution!
        
        Please file this form by replacing markdown commentary
        tags with the text. If section needs in no action - remove it.
   
        Also remember, that CouchDB uses the Review-Then-Commit (RTC) model 
        of code collaboration. Positive feedback provides by +1 from committers
        while negative by -1. The -1 also means veto and need to be addressed
        to find the consensus. Once there are no objections, PR could be merged.
   
        See: http://couchdb.apache.org/bylaws.html#decisions for more info -->
   
   ## Overview
   
   This adds a test to ensure that the changes_listener process exits when
   the mem3_shards process is shut down.
   
   ## Testing recommendations
   
   <!-- Describe how we can test your changes.
        Does it provides any behaviour that the end users 
        could notice? -->
   
   N/A
   
   ## JIRA issue number
   
   COUCHDB-3398
   
   <!-- If this is a significant change, please file a JIRA issue at:
        https://issues.apache.org/jira/browse/COUCHDB
        and include the number here and in commit message(s)  -->
   
   ## Related Pull Requests
   
   <!-- If your changes affects on multiple components in different 
        repositories please list here links to those pull requests.  -->
   
   ## Checklist
   
   - [x] Code is written and works correctly;
   - [x] Changes are tests;
   - [x] Documentation reflects the changes;
   - [x] It's not necessary to update [rebar.config.script] (https://github.com/apache/couchdb/blob/master/rebar.config.script)
         with the correct commit hash once this PR get merged.
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services