You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Vikas Kumar (Jira)" <ji...@apache.org> on 2025/08/12 10:59:00 UTC
[jira] [Resolved] (RANGER-5280) TestKMSMetricsWrapper unit test case is failing
[ https://issues.apache.org/jira/browse/RANGER-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vikas Kumar resolved RANGER-5280.
---------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Corresponding PR has been reviewed and merged. Please find below the commit details:
{code:java}
commit f074e4277d744a2ee526d24068f878fa0e409c9b
Author: Vikas Kumar <ta...@gmail.com>
Date: Fri Aug 8 19:10:26 2025 +0530
RANGER-5280: Fix for test case failure in TestKMSMetricsWrapper (#625)
{code}
hence resolving the JIRA.
> TestKMSMetricsWrapper unit test case is failing
> -----------------------------------------------
>
> Key: RANGER-5280
> URL: https://issues.apache.org/jira/browse/RANGER-5280
> Project: Ranger
> Issue Type: Bug
> Components: kms
> Reporter: Vikas Kumar
> Assignee: Vikas Kumar
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After recent KMS UT merges , TestKMSMetricsWrapper has started failing. And it is not always failing, it's intermittent.
> {*}Reason{*}: New test cases now creates more keys and hence metric counter is increasing.
> In TestKMSMetricsWrapper, it is incrementing by one and asserting with one as expected value.
> *Failure scenario:* Other Test cases ( that creates keys) get executed first, and it will increase the counter to that many number of keys, Say 2.
> Now in TestKMSMetricsWrapper, it increments by one and expects one but actual is 3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)