[MAPREDUCE-6088] TestTokenCache tests should use their own JobConf instances

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: mrv1, test
• Hadoop Flags: Reviewed
• Assignee: Zhihai Xu
• Reporter: Zhihai Xu
• Created: 13/Sep/14 01:18
• Updated: 19/Sep/14 22:21
• Resolved: 19/Sep/14 19:00

Description

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.

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