Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57CBFE83E for ; Wed, 2 Jan 2013 22:56:13 +0000 (UTC) Received: (qmail 54632 invoked by uid 500); 2 Jan 2013 22:56:12 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 54579 invoked by uid 500); 2 Jan 2013 22:56:12 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 54563 invoked by uid 99); 2 Jan 2013 22:56:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 22:56:12 +0000 Date: Wed, 2 Jan 2013 22:56:12 +0000 (UTC) From: "Arpit Agarwal (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-9174) TestSecurityUtil failure on Windows with Open JDK 7 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HADOOP-9174: ---------------------------------- Description: TestSecurityUtil.TestBuildTokenServiceSockAddr fails due to implicit dependency on the test case execution order. Testcase: testBuildTokenServiceSockAddr took 0.003 sec Caused an ERROR expected:<[127.0.0.1]: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. was: TestSecurityUtil.TestBuildTokenServiceSockAddr fails due to implicit dependency on the test case execution order. Testcase: testBuildTokenServiceSockAddr took 0.003 sec Caused an ERROR expected:<[127.0.0.1]:123> but was:<[localhost]:123> at org.apache.hadoop.security.TestSecurityUtil.testBuildTokenServiceSockAddr(TestSecurityUtil.java:133) Similar bug exists in TestSecurityUtil.testBuildDTServiceName. > 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:<[127.0.0.1]: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