[ https://issues.apache.org/jira/browse/HADOOP-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins reassigned HADOOP-7290: ----------------------------------- Assignee: Trevor Robinson > Unit test failure in TestUserGroupInformation.testGetServerSideGroups > --------------------------------------------------------------------- > > Key: HADOOP-7290 > URL: https://issues.apache.org/jira/browse/HADOOP-7290 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 0.23.0 > Environment: Linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 > 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux > Java(TM) SE Runtime Environment (build 1.6.0_24-b07) > Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) > Reporter: Trevor Robinson > Assignee: Trevor Robinson > Priority: Minor > Labels: test > Attachments: TestUserGroupInformation-id-order.patch > > > Testsuite: org.apache.hadoop.security.TestUserGroupInformation > Tests run: 14, Failures: 1, Errors: 0, Time elapsed: 0.278 sec > ------------- Standard Output --------------- > trobinson:users guest git > ------------- ---------------- --------------- > Testcase: testGetServerSideGroups took 0.051 sec > FAILED > expected:<g[ues]t> but was:<g[i]t> > junit.framework.AssertionFailedError: expected:<g[ues]t> but was:<g[i]t> > at > org.apache.hadoop.security.TestUserGroupInformation.testGetServerSideGroups(TestUserGroupInformation.java:94) > It seems like the test is assuming that the groups returned by > UserGroupInformation.getGroupNames() are in the same order as those returned > by executing `id -Gn`. getGroupNames() only documents that the primary group > is first, and `man id` doesn't document any ordering, so it seems like the > test needs to be reworked to remove that assumption. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira