hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9174) TestSecurityUtil failure on Windows with Open JDK 7
Date Wed, 02 Jan 2013 23:02:12 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542518#comment-13542518

Suresh Srinivas commented on HADOOP-9174:

+1. There were similar test failures fixed in trunk. Is this change also required for trunk?
> TestSecurityUtil failure on Windows with Open JDK 7
> ---------------------------------------------------
>                 Key: HADOOP-9174
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9174
>             Project: Hadoop Common
>          Issue Type: Test
>    Affects Versions: 1-win
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: HADOOP-9174.patch
> TestSecurityUtil.TestBuildTokenServiceSockAddr fails due to implicit dependency on the
test case execution order.
> Testcase: testBuildTokenServiceSockAddr took 0.003 sec
> 	Caused an ERROR
> expected:<[]:123> but was:<[localhost]:123>
> 	at org.apache.hadoop.security.TestSecurityUtil.testBuildTokenServiceSockAddr(TestSecurityUtil.java:133)
> Similar bug exists in TestSecurityUtil.testBuildDTServiceName.
> The root cause is that a helper routine (verifyAddress) used by some test cases has a
side effect. It resets a static variable (SecurityUtil.useIpForTokenService). 
> The broken test cases assume that the flag will be set to true when they are invoked.
The fix is to explicitly initialize the flag to its expected value instead of depending on
the execution order.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message