You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by da...@apache.org on 2017/04/18 19:07:40 UTC
[couchdb] 01/01: Fix mem3_sync_event_listener unit test
This is an automated email from the ASF dual-hosted git repository.
davisp pushed a commit to branch COUCHDB-3380-fix-mem3-sync-event-listener-unit-tests
in repository https://gitbox.apache.org/repos/asf/couchdb.git
commit c0fda54d3ed4f06f1e41db598859de23aaf0e3ac
Author: Paul J. Davis <pa...@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.
COUCHDB-3380
---
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" <co...@couchdb.apache.org>.