You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2017/04/27 23:56:04 UTC

[jira] [Updated] (SENTRY-1721) Unit test failures in TestSentryStore due to changeId miscount

     [ https://issues.apache.org/jira/browse/SENTRY-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Kolbasov updated SENTRY-1721:
---------------------------------------
    Summary: Unit test failures in TestSentryStore due to changeId miscount  (was: Unit test failures in TestSentryStore)

> Unit test failures in TestSentryStore due to changeId miscount
> --------------------------------------------------------------
>
>                 Key: SENTRY-1721
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1721
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Na Li
>            Assignee: Na Li
>              Labels: test
>             Fix For: sentry-ha-redesign
>
>         Attachments: SENTRY-1721.001-sentry-ha-redesign.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> We encounter multiple incidents of unit test failures. They are mainly TestSentryStore.testPrivilegesWithPermUpdate and TestPrivilegeOperatePersistence.testGrantPrivilegeExternalComponentInvalidConf
> These tests fail more often when HMSFollower is created after SentryService.Start() is called. And less frequent when HMSFollower is created in SentryService constructor. Need investigation on whether this is just a bug in test cases or reflect issues in synchronization between Sentry HMS metastore.



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