couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dav...@apache.org
Subject [couchdb] 01/03: Fix mem3_sync_event_listener unit test
Date Thu, 06 Apr 2017 17:35:59 GMT
This is an automated email from the ASF dual-hosted git repository.

davisp pushed a commit to branch COUCHDB-3287-pluggable-storage-engines
in repository https://gitbox.apache.org/repos/asf/couchdb.git

commit c4dfee4dbc595a4616836d402e71d116a9207670
Author: Paul J. Davis <paul.joseph.davis@gmail.com>
AuthorDate: Thu Feb 2 11:23:16 2017 -0600

    Fix mem3_sync_event_listener unit test
    
    The `should_restart_listener` test was failing because the pattern
    supplied to meck was wrong. The argument to
    `config_notifier:handle_event/2` is of the pattern `{config_change,
    Section, Key, Value, Persist}` but the test was only matching a
    four-tuple which I assume was missing the `config_change` atom in the
    argument.
---
 src/mem3/src/mem3_sync_event_listener.erl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/mem3/src/mem3_sync_event_listener.erl b/src/mem3/src/mem3_sync_event_listener.erl
index 7859c31..cd671e4 100644
--- a/src/mem3/src/mem3_sync_event_listener.erl
+++ b/src/mem3/src/mem3_sync_event_listener.erl
@@ -223,7 +223,7 @@ setup() ->
 
     ok = meck:new(config_notifier, [passthrough]),
     ok = meck:expect(config_notifier, handle_event, [
-        {[{'_', '_', "error", '_'}, '_'], meck:raise(throw, raised_error)},
+        {[{'_', '_', '_', "error", '_'}, '_'], meck:raise(throw, raised_error)},
         {['_', '_'], meck:passthrough()}
     ]),
 

-- 
To stop receiving notification emails like this one, please contact
"commits@couchdb.apache.org" <commits@couchdb.apache.org>.

Mime
View raw message