Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1557

TestFsActionExecutor.testChmodWithGlob fails against Hadoop 2.1.x-beta

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • trunk
    • 4.1.0
    • tests
    • None

    Description

      When running against Hadoop 2.1.x-beta, TestFsActionExecutor.testChmodWithGlob fails because of an incompatible change introduced by HDFS-4659 with how file permissions are set.

      -------------------------------------------------------------------------------
      Test set: org.apache.oozie.action.hadoop.TestFsActionExecutor
      -------------------------------------------------------------------------------
      Tests run: 24, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.813 sec <<< FAILURE!
      testChmodWithGlob(org.apache.oozie.action.hadoop.TestFsActionExecutor)  Time elapsed: 0.002 sec  <<< FAILURE!
      junit.framework.ComparisonFailure: expected:<rw[-]------> but was:<rw[x]------>
      	at junit.framework.Assert.assertEquals(Assert.java:85)
      	at junit.framework.Assert.assertEquals(Assert.java:91)
      	at org.apache.oozie.action.hadoop.TestFsActionExecutor.testChmodWithGlob(TestFsActionExecutor.java:468)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at junit.framework.TestCase.runTest(TestCase.java:168)
      	at junit.framework.TestCase.runBare(TestCase.java:134)
      	at junit.framework.TestResult$1.protect(TestResult.java:110)
      	at junit.framework.TestResult.runProtected(TestResult.java:128)
      	at junit.framework.TestResult.run(TestResult.java:113)
      	at junit.framework.TestCase.run(TestCase.java:124)
      	at junit.framework.TestSuite.runTest(TestSuite.java:243)
      	at junit.framework.TestSuite.run(TestSuite.java:238)
      	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
      	at org.apache.maven.surefire.junitcore.ClassDemarcatingRunner.run(ClassDemarcatingRunner.java:58)
      	at org.junit.runners.Suite.runChild(Suite.java:128)
      	at org.junit.runners.Suite.runChild(Suite.java:24)
      	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
      	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
      	at java.lang.Thread.run(Thread.java:680)
      

      As this behavior is different between Hadoop 1 and 2, I think we should simply have the test not check for this case.

      Attachments

        1. OOZIE-1557.patch
          1 kB
          Robert Kanter

        Issue Links

        Activity

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

          People

            rkanter Robert Kanter
            rkanter Robert Kanter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment