[
https://issues.apache.org/jira/browse/HIVE-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szehon Ho updated HIVE-7154:
----------------------------
Attachment: HIVE-7154.2.patch
Looked at the test report and found they are run in this order (that is
different on my machine): testMetricsMBean, testScopeConcurrency ,
testScopeSingleThread.
Adding "endScope" in #testScopeConcurrency in addition to "startScope", so the
next test has a clean state.
I manually ran the tests in this order, and in several other orders, to verify.
Hope this works.
> TestMetrics fails intermittently on the trunk
> ---------------------------------------------
>
> Key: HIVE-7154
> URL: https://issues.apache.org/jira/browse/HIVE-7154
> Project: Hive
> Issue Type: Bug
> Components: Tests
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: HIVE-7154.2.patch, HIVE-7154.patch
>
>
> TestMetrics fails intermittently on trunk, with:
> {noformat}
> java.io.IOException: No metrics scope named foo
> at
> org.apache.hadoop.hive.common.metrics.Metrics.getScope(Metrics.java:222)
> at
> org.apache.hadoop.hive.common.metrics.TestMetrics.testScopeConcurrency(TestMetrics.java:215)
> {noformat}
> Not able to prove it, but seems like it may depend on the test order. For
> example, if I just run "testScopeConcurrency" by itself then it fails because
> the metric is not initialized. If I run the entire test then it will succeed
> because the metric is initialized by the other tests.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
