You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2014/09/19 20:57:34 UTC
[jira] [Updated] (MAPREDUCE-6088) TestTokenCache tests should use
their own JobConf instances
[ https://issues.apache.org/jira/browse/MAPREDUCE-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthik Kambatla updated MAPREDUCE-6088:
----------------------------------------
Summary: TestTokenCache tests should use their own JobConf instances (was: TestTokenCache in mrv1 (branch-1) depend on the order of test execution. testLocalJobTokenCache will fail if it execute after testTokenCache.)
> TestTokenCache tests should use their own JobConf instances
> -----------------------------------------------------------
>
> Key: MAPREDUCE-6088
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6088
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv1, test
> Reporter: zhihai xu
> Assignee: zhihai xu
> Attachments: MAPREDUCE-6088.branch-1.0.patch, MAPREDUCE-6088.branch-1.1.patch
>
>
> TestTokenCache in mrv1 (branch-1) depend on the order of test execution. testLocalJobTokenCache will fail if it executed after testTokenCache.
> The reason is because testLocalJobTokenCache depends on the jConf setup by testTokenCache.
> The fix is to set up the JobConf separately for testLocalJobTokenCache and testTokenCache.
> See the following test result.
> {noformat}
> Testcase: testLocalJobTokenCache took 1.197 sec
> FAILED
> local Job failed
> junit.framework.AssertionFailedError: local Job failed
> at org.apache.hadoop.mapreduce.security.TestTokenCache.testLocalJobTokenCache(TestTokenCache.java:258)
> Testcase: testGetTokensForNamenodes took 0.003 sec
> Testcase: testGetTokensForUriWithoutAuth took 0.01 sec
> Testcase: testCleanUpTokenReferral took 0.014 sec
> Testcase: testTokenCache took 13.316 sec
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)