[jira] [Commented] (COUCHDB-3380) Fix mem3_sync_event_listener unit tests

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973310#comment-15973310 ] 

ASF subversion and git services commented on COUCHDB-3380:
----------------------------------------------------------

Commit c0fda54d3ed4f06f1e41db598859de23aaf0e3ac in couchdb's branch refs/heads/COUCHDB-3380-fix-mem3-sync-event-listener-unit-tests from [~paul.joseph.davis]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=c0fda54 ]

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


> Fix mem3_sync_event_listener unit tests
> ---------------------------------------
>
>                 Key: COUCHDB-3380
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3380
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>            Reporter: Paul Joseph Davis
>
> The tests in mem3_sync_event_listener get skipped because of meck issues but if you run the mem3 eunit tests directly (i.e., make eunit apps=mem3) you'll see this failure. The change is pretty trivial. Just a matter of this test never having run in CI because reasons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)