Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-7290

Unit test failure in TestUserGroupInformation.testGetServerSideGroups

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 0.23.0
    • None
    • security
    • 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)

    • Reviewed

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            scurrilous Trevor Robinson
            scurrilous Trevor Robinson
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment