You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/09 11:29:44 UTC
[jira] [Commented] (HIVE-3487) Some of the Metastore unit tests
failing on Windows because of the static variables initialization problem
in HiveConf class.
[ https://issues.apache.org/jira/browse/HIVE-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548168#comment-13548168 ]
Hudson commented on HIVE-3487:
------------------------------
Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
HIVE-3487 : Some of the Metastore unit tests failing on Windows because of the static variables initialization problem in HiveConf class. (Kanna Karanam via Ashutosh Chauhan) (Revision 1388112)
Result = ABORTED
hashutosh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1388112
Files :
* /hive/trunk/metastore/src/test/org/apache/hadoop/hive/metastore/TestMarkPartition.java
* /hive/trunk/metastore/src/test/org/apache/hadoop/hive/metastore/TestMetaStoreEventListener.java
> Some of the Metastore unit tests failing on Windows because of the static variables initialization problem in HiveConf class.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-3487
> URL: https://issues.apache.org/jira/browse/HIVE-3487
> Project: Hive
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.10.0, 0.9.1
> Reporter: Kanna Karanam
> Assignee: Kanna Karanam
> Fix For: 0.10.0
>
> Attachments: HIVE-3487.1.patch.txt
>
>
> Following unit tests are failing on windows because of the problem with static variables initialization.
> TestMarkPartition
> TestMarkRemotePartition
> TestMetastoreEventListener
> Reason – Static variables on outer class static variables are not getting initialized when we reference nested public static class variables on windows.
--
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