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:39 UTC
[couchdb] branch
COUCHDB-3380-fix-mem3-sync-event-listener-unit-tests updated (9122d73 ->
c0fda54)
This is an automated email from the ASF dual-hosted git repository.
davisp pushed a change to branch COUCHDB-3380-fix-mem3-sync-event-listener-unit-tests
in repository https://gitbox.apache.org/repos/asf/couchdb.git.
discards 9122d73 Fix mem3_sync_event_listener unit test
omits d754c8c Fix couch_auth_cache reinitialization logic
new c0fda54 Fix mem3_sync_event_listener unit test
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (9122d73)
\
N -- N -- N refs/heads/COUCHDB-3380-fix-mem3-sync-event-listener-unit-tests (c0fda54)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
src/couch/src/couch_auth_cache.erl | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
--
To stop receiving notification emails like this one, please contact
['"commits@couchdb.apache.org" <co...@couchdb.apache.org>'].
[couchdb] 01/01: Fix mem3_sync_event_listener unit test
Posted by da...@apache.org.
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>.