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

Naveen Gangam updated HIVE-14313:
---------------------------------
    Attachment: HIVE-14313.patch

[~szehon] Could you please review the patch? Looks like the patch is relying on 
the initial count being 1. In my local run of the unit tests, the initial count 
for OPEN_CONNECTIONS was ZERO, where as on the jenkins machine, the initial 
count appears to be 2. 

The test shouldnt care as much what the initial count was, we only want to 
ensure that the count moves up or down when new clients connect/disconnect. Let 
me know if this makes sense. Thanks

> Test failure TestMetaStoreMetrics.testConnections
> -------------------------------------------------
>
>                 Key: HIVE-14313
>                 URL: https://issues.apache.org/jira/browse/HIVE-14313
>             Project: Hive
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 2.2.0
>            Reporter: Naveen Gangam
>            Assignee: Naveen Gangam
>         Attachments: HIVE-14313.patch
>
>
> Looks like this test has been failing for the past 84 builds prior to
> https://builds.apache.org/job/PreCommit-HIVE-MASTER-Build/597/testReport/org.apache.hadoop.hive.metastore/TestMetaStoreMetrics/testConnections/
> org.apache.hadoop.hive.metastore.TestMetaStoreMetrics.testConnections
> Failing for the past 84 builds (Since #514 )
> Took 28 ms.
> Error Message
> expected:<[1]> but was:<[2]>
> Stacktrace
> org.junit.ComparisonFailure: expected:<[1]> but was:<[2]>
>       at org.junit.Assert.assertEquals(Assert.java:115)
>       at org.junit.Assert.assertEquals(Assert.java:144)
>       at 
> org.apache.hadoop.hive.common.metrics.MetricsTestUtils.verifyMetricsJson(MetricsTestUtils.java:50)
>       at 
> org.apache.hadoop.hive.metastore.TestMetaStoreMetrics.testConnections(TestMetaStoreMetrics.java:146)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to