Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-5213

Fix a bug in LogCLIHelpers which cause TestLogsCLI#testFetchApplictionLogs fails intermittently

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.0, 3.0.0-alpha1
    • Component/s: test
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      TestLogsCLI fails intermittently on build link

      Running org.apache.hadoop.yarn.client.cli.TestLogsCLI
      Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.708 sec <<< FAILURE! - in org.apache.hadoop.yarn.client.cli.TestLogsCLI
      testFetchApplictionLogs(org.apache.hadoop.yarn.client.cli.TestLogsCLI)  Time elapsed: 0.176 sec  <<< FAILURE!
      org.junit.ComparisonFailure: expected:<[Hello]> but was:<[=====]>
      	at org.junit.Assert.assertEquals(Assert.java:115)
      	at org.junit.Assert.assertEquals(Assert.java:144)
      	at org.apache.hadoop.yarn.client.cli.TestLogsCLI.testFetchApplictionLogs(TestLogsCLI.java:389)
      
      1. YARN-5213.1.patch
        1 kB
        Xuan Gong
      2. YARN-5213.2.patch
        11 kB
        Xuan Gong
      3. YARN-5213.patch
        2 kB
        Rohith Sharma K S

        Activity

        Hide
        rohithsharma Rohith Sharma K S added a comment -

        cc :-\ Xuan Gong

        Show
        rohithsharma Rohith Sharma K S added a comment - cc :-\ Xuan Gong
        Hide
        rohithsharma Rohith Sharma K S added a comment -

        Recent build failure for this test case Link

        Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.353 sec <<< FAILURE! - in org.apache.hadoop.yarn.client.cli.TestLogsCLI
        testFetchFinishedApplictionLogs(org.apache.hadoop.yarn.client.cli.TestLogsCLI)  Time elapsed: 0.214 sec  <<< FAILURE!
        org.junit.ComparisonFailure: expected:<[Hello]> but was:<[=====]>
        	at org.junit.Assert.assertEquals(Assert.java:115)
        	at org.junit.Assert.assertEquals(Assert.java:144)
        	at org.apache.hadoop.yarn.client.cli.TestLogsCLI.testFetchFinishedApplictionLogs(TestLogsCLI.java:427)
        
        Show
        rohithsharma Rohith Sharma K S added a comment - Recent build failure for this test case Link Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.353 sec <<< FAILURE! - in org.apache.hadoop.yarn.client.cli.TestLogsCLI testFetchFinishedApplictionLogs(org.apache.hadoop.yarn.client.cli.TestLogsCLI) Time elapsed: 0.214 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[Hello]> but was:<[=====]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.hadoop.yarn.client.cli.TestLogsCLI.testFetchFinishedApplictionLogs(TestLogsCLI.java:427)
        Hide
        rohithsharma Rohith Sharma K S added a comment -

        I looked at the test case for randomness, basically test testFetchFinishedApplictionLogs usually failing in Ubuntu but not either in Windows OR Mac. The reason is test is expecting whenever container logs files are read, log files are listed in order which LogCliHelper print on console. The test-case reads it and try to do assertion. But FileContext.getFileContext(qualifiedLogDir.toUri(), getConf()).listStatus(remoteAppLogDir) RemoteIterator does not guaranty that iterator is in-order. As a result, printing on console might get randomized for the log files.
        Test failing randomly because test always assert content from specific offset which might go on toss

           Assert.assertEquals(new String(logMessage.getBytes(), 0, 5),
                new String(sysOutStream.toByteArray(),
                (fullContextSize - fileContentSize - tailContentSize), 5));
        
        Show
        rohithsharma Rohith Sharma K S added a comment - I looked at the test case for randomness, basically test testFetchFinishedApplictionLogs usually failing in Ubuntu but not either in Windows OR Mac. The reason is test is expecting whenever container logs files are read, log files are listed in order which LogCliHelper print on console. The test-case reads it and try to do assertion. But FileContext.getFileContext(qualifiedLogDir.toUri(), getConf()).listStatus(remoteAppLogDir) RemoteIterator does not guaranty that iterator is in-order. As a result, printing on console might get randomized for the log files. Test failing randomly because test always assert content from specific offset which might go on toss Assert.assertEquals( new String (logMessage.getBytes(), 0, 5), new String (sysOutStream.toByteArray(), (fullContextSize - fileContentSize - tailContentSize), 5));
        Hide
        rohithsharma Rohith Sharma K S added a comment -

        Expected ByteArrayStream

        Container: container_0_0001_01_000003 on localhost_12341468825226852
        ====================================================================
        Container: container_0_0001_01_000003 on localhost_12341468825227186
        ====================================================================
        Container: container_0_0001_01_000003 on localhost_12341468825227197
        ====================================================================
        Container: container_0_0001_01_000003 on localhost_12341468825227236
        ====================================================================
        Container: container_0_0001_01_000003 on localhost_12341468825227248
        ====================================================================
        LogType:stdout
        Log Upload Time:Mon Jul 18 12:30:27 +0530 2016
        LogLength:43
        Log Contents:
        Hello
        End of LogType:stdout
        
        
        

        But actual ByteArrayStream is

        Container: container_0_0001_01_000003 on localhost_12341468824484792
        ====================================================================
        Container: container_0_0001_01_000003 on localhost_12341468824484591
        ====================================================================
        Container: container_0_0001_01_000003 on localhost_12341468824485086
        ====================================================================
        LogType:stdout
        Log Upload Time:Mon Jul 18 12:18:05 +0530 2016
        LogLength:43
        Log Contents:
        Hello container_0_0001_01_000003 in stdout!
        End of LogType:stdout
        
        Container: container_0_0001_01_000003 on localhost_12341468824484822
        ====================================================================
        Container: container_0_0001_01_000003 on localhost_12341468824485037
        ====================================================================
        
        Show
        rohithsharma Rohith Sharma K S added a comment - Expected ByteArrayStream Container: container_0_0001_01_000003 on localhost_12341468825226852 ==================================================================== Container: container_0_0001_01_000003 on localhost_12341468825227186 ==================================================================== Container: container_0_0001_01_000003 on localhost_12341468825227197 ==================================================================== Container: container_0_0001_01_000003 on localhost_12341468825227236 ==================================================================== Container: container_0_0001_01_000003 on localhost_12341468825227248 ==================================================================== LogType:stdout Log Upload Time:Mon Jul 18 12:30:27 +0530 2016 LogLength:43 Log Contents: Hello End of LogType:stdout But actual ByteArrayStream is Container: container_0_0001_01_000003 on localhost_12341468824484792 ==================================================================== Container: container_0_0001_01_000003 on localhost_12341468824484591 ==================================================================== Container: container_0_0001_01_000003 on localhost_12341468824485086 ==================================================================== LogType:stdout Log Upload Time:Mon Jul 18 12:18:05 +0530 2016 LogLength:43 Log Contents: Hello container_0_0001_01_000003 in stdout! End of LogType:stdout Container: container_0_0001_01_000003 on localhost_12341468824484822 ==================================================================== Container: container_0_0001_01_000003 on localhost_12341468824485037 ====================================================================
        Hide
        hadoopqa Hadoop QA added a comment -
        -1 overall



        Vote Subsystem Runtime Comment
        0 reexec 0m 17s Docker mode activated.
        +1 @author 0m 0s The patch does not contain any @author tags.
        +1 test4tests 0m 0s The patch appears to include 1 new or modified test files.
        +1 mvninstall 7m 5s trunk passed
        +1 compile 0m 20s trunk passed
        +1 checkstyle 0m 15s trunk passed
        +1 mvnsite 0m 26s trunk passed
        +1 mvneclipse 0m 16s trunk passed
        +1 findbugs 0m 30s trunk passed
        +1 javadoc 0m 14s trunk passed
        +1 mvninstall 0m 18s the patch passed
        +1 compile 0m 17s the patch passed
        +1 javac 0m 17s the patch passed
        -1 checkstyle 0m 12s hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client: The patch generated 1 new + 84 unchanged - 1 fixed = 85 total (was 85)
        +1 mvnsite 0m 22s the patch passed
        +1 mvneclipse 0m 12s the patch passed
        +1 whitespace 0m 0s The patch has no whitespace issues.
        +1 findbugs 0m 33s the patch passed
        +1 javadoc 0m 11s the patch passed
        -1 unit 8m 13s hadoop-yarn-client in the patch failed.
        +1 asflicense 0m 16s The patch does not generate ASF License warnings.
        20m 33s



        Reason Tests
        Failed junit tests hadoop.yarn.client.api.impl.TestYarnClient



        Subsystem Report/Notes
        Docker Image:yetus/hadoop:9560f25
        JIRA Patch URL https://issues.apache.org/jira/secure/attachment/12818536/YARN-5213.patch
        JIRA Issue YARN-5213
        Optional Tests asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle
        uname Linux eb52deffa530 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
        Build tool maven
        Personality /testptch/hadoop/patchprocess/precommit/personality/provided.sh
        git revision trunk / 5b4a708
        Default Java 1.8.0_91
        findbugs v3.0.0
        checkstyle https://builds.apache.org/job/PreCommit-YARN-Build/12355/artifact/patchprocess/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
        unit https://builds.apache.org/job/PreCommit-YARN-Build/12355/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
        unit test logs https://builds.apache.org/job/PreCommit-YARN-Build/12355/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
        Test Results https://builds.apache.org/job/PreCommit-YARN-Build/12355/testReport/
        modules C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
        Console output https://builds.apache.org/job/PreCommit-YARN-Build/12355/console
        Powered by Apache Yetus 0.3.0 http://yetus.apache.org

        This message was automatically generated.

        Show
        hadoopqa Hadoop QA added a comment - -1 overall Vote Subsystem Runtime Comment 0 reexec 0m 17s Docker mode activated. +1 @author 0m 0s The patch does not contain any @author tags. +1 test4tests 0m 0s The patch appears to include 1 new or modified test files. +1 mvninstall 7m 5s trunk passed +1 compile 0m 20s trunk passed +1 checkstyle 0m 15s trunk passed +1 mvnsite 0m 26s trunk passed +1 mvneclipse 0m 16s trunk passed +1 findbugs 0m 30s trunk passed +1 javadoc 0m 14s trunk passed +1 mvninstall 0m 18s the patch passed +1 compile 0m 17s the patch passed +1 javac 0m 17s the patch passed -1 checkstyle 0m 12s hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client: The patch generated 1 new + 84 unchanged - 1 fixed = 85 total (was 85) +1 mvnsite 0m 22s the patch passed +1 mvneclipse 0m 12s the patch passed +1 whitespace 0m 0s The patch has no whitespace issues. +1 findbugs 0m 33s the patch passed +1 javadoc 0m 11s the patch passed -1 unit 8m 13s hadoop-yarn-client in the patch failed. +1 asflicense 0m 16s The patch does not generate ASF License warnings. 20m 33s Reason Tests Failed junit tests hadoop.yarn.client.api.impl.TestYarnClient Subsystem Report/Notes Docker Image:yetus/hadoop:9560f25 JIRA Patch URL https://issues.apache.org/jira/secure/attachment/12818536/YARN-5213.patch JIRA Issue YARN-5213 Optional Tests asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle uname Linux eb52deffa530 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Build tool maven Personality /testptch/hadoop/patchprocess/precommit/personality/provided.sh git revision trunk / 5b4a708 Default Java 1.8.0_91 findbugs v3.0.0 checkstyle https://builds.apache.org/job/PreCommit-YARN-Build/12355/artifact/patchprocess/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt unit https://builds.apache.org/job/PreCommit-YARN-Build/12355/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt unit test logs https://builds.apache.org/job/PreCommit-YARN-Build/12355/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt Test Results https://builds.apache.org/job/PreCommit-YARN-Build/12355/testReport/ modules C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client Console output https://builds.apache.org/job/PreCommit-YARN-Build/12355/console Powered by Apache Yetus 0.3.0 http://yetus.apache.org This message was automatically generated.
        Hide
        djp Junping Du added a comment -

        Thanks Rohith Sharma K S for investigation on this. I run into the same issue and see the same behavior as you. However, for test case, I think only one record for container 3 is expected. I guess there is something wrong with logsCLI but not only test cases. CC Xuan Gong.

        Show
        djp Junping Du added a comment - Thanks Rohith Sharma K S for investigation on this. I run into the same issue and see the same behavior as you. However, for test case, I think only one record for container 3 is expected. I guess there is something wrong with logsCLI but not only test cases. CC Xuan Gong .
        Hide
        djp Junping Du added a comment -

        Change the issue type to a bug as this is not only a test issue.

        Show
        djp Junping Du added a comment - Change the issue type to a bug as this is not only a test issue.
        Hide
        xgong Xuan Gong added a comment -

        Thanks for the investigation. Rohith Sharma K S.
        Agree with Junping Du. This is the code bug, not the test issue.

        Uploaded a patch to fix it.

        Show
        xgong Xuan Gong added a comment - Thanks for the investigation. Rohith Sharma K S . Agree with Junping Du . This is the code bug, not the test issue. Uploaded a patch to fix it.
        Hide
        rohithsharma Rohith Sharma K S added a comment -

        One quick comment,

        1. reader creation is duplicated, may be this can be avoided.
        Show
        rohithsharma Rohith Sharma K S added a comment - One quick comment, reader creation is duplicated, may be this can be avoided.
        Hide
        djp Junping Du added a comment -

        Thanks Xuan Gong for put a quick patch and Rohith Sharma K S for quick comments!
        I think this patch fix an issue for log rolling correctly and I verified the patch locally and previous test failure is gone.
        A couple of comments:

        reader creation is duplicated, may be this can be avoided.

        This is also my thought when I first look. However, after taking a look again especially sync with Xuan offline, I agree this should be by intentional as reader's stream index could be updated after calling getContainerLogsStream(). However, we should add a comments there to explicitly mention that why we need a "duplicated" creation here or later comer could be confused also and did mistakenly change.

        In TestLogsCLI.java,

        int tailContentSize = "\nEnd of LogType:syslog\n\n".getBytes().length;
        

        This is not right. Here LogType should be stdout but not syslog although not affect result yet.

        One optional comments to see if you would like to address here or later: there are many hard coded messages, like: "Hello container_0_0001_01_000003 in stdout!" - better to have static method with specifying container id and logtype.

        Show
        djp Junping Du added a comment - Thanks Xuan Gong for put a quick patch and Rohith Sharma K S for quick comments! I think this patch fix an issue for log rolling correctly and I verified the patch locally and previous test failure is gone. A couple of comments: reader creation is duplicated, may be this can be avoided. This is also my thought when I first look. However, after taking a look again especially sync with Xuan offline, I agree this should be by intentional as reader's stream index could be updated after calling getContainerLogsStream() . However, we should add a comments there to explicitly mention that why we need a "duplicated" creation here or later comer could be confused also and did mistakenly change. In TestLogsCLI.java, int tailContentSize = "\nEnd of LogType:syslog\n\n".getBytes().length; This is not right. Here LogType should be stdout but not syslog although not affect result yet. One optional comments to see if you would like to address here or later: there are many hard coded messages, like: "Hello container_0_0001_01_000003 in stdout!" - better to have static method with specifying container id and logtype.
        Hide
        xgong Xuan Gong added a comment -

        Uploaded a new patch to address all the comments

        Show
        xgong Xuan Gong added a comment - Uploaded a new patch to address all the comments
        Hide
        hadoopqa Hadoop QA added a comment -
        -1 overall



        Vote Subsystem Runtime Comment
        0 reexec 0m 22s Docker mode activated.
        +1 @author 0m 0s The patch does not contain any @author tags.
        +1 test4tests 0m 0s The patch appears to include 1 new or modified test files.
        0 mvndep 0m 10s Maven dependency ordering for branch
        +1 mvninstall 6m 59s trunk passed
        +1 compile 2m 26s trunk passed
        +1 checkstyle 0m 40s trunk passed
        +1 mvnsite 0m 56s trunk passed
        +1 mvneclipse 0m 28s trunk passed
        +1 findbugs 1m 29s trunk passed
        +1 javadoc 0m 42s trunk passed
        0 mvndep 0m 10s Maven dependency ordering for patch
        +1 mvninstall 0m 46s the patch passed
        +1 compile 2m 23s the patch passed
        +1 javac 2m 23s the patch passed
        +1 checkstyle 0m 37s hadoop-yarn-project/hadoop-yarn: The patch generated 0 new + 83 unchanged - 4 fixed = 83 total (was 87)
        +1 mvnsite 0m 53s the patch passed
        +1 mvneclipse 0m 24s the patch passed
        +1 whitespace 0m 0s The patch has no whitespace issues.
        +1 findbugs 1m 43s the patch passed
        +1 javadoc 0m 39s the patch passed
        +1 unit 2m 16s hadoop-yarn-common in the patch passed.
        -1 unit 8m 17s hadoop-yarn-client in the patch failed.
        +1 asflicense 0m 17s The patch does not generate ASF License warnings.
        33m 21s



        Reason Tests
        Failed junit tests hadoop.yarn.client.api.impl.TestYarnClient



        Subsystem Report/Notes
        Docker Image:yetus/hadoop:9560f25
        JIRA Patch URL https://issues.apache.org/jira/secure/attachment/12818654/YARN-5213.2.patch
        JIRA Issue YARN-5213
        Optional Tests asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle
        uname Linux 877271c769fe 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
        Build tool maven
        Personality /testptch/hadoop/patchprocess/precommit/personality/provided.sh
        git revision trunk / 92fe2db
        Default Java 1.8.0_91
        findbugs v3.0.0
        unit https://builds.apache.org/job/PreCommit-YARN-Build/12361/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
        unit test logs https://builds.apache.org/job/PreCommit-YARN-Build/12361/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
        Test Results https://builds.apache.org/job/PreCommit-YARN-Build/12361/testReport/
        modules C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client U: hadoop-yarn-project/hadoop-yarn
        Console output https://builds.apache.org/job/PreCommit-YARN-Build/12361/console
        Powered by Apache Yetus 0.3.0 http://yetus.apache.org

        This message was automatically generated.

        Show
        hadoopqa Hadoop QA added a comment - -1 overall Vote Subsystem Runtime Comment 0 reexec 0m 22s Docker mode activated. +1 @author 0m 0s The patch does not contain any @author tags. +1 test4tests 0m 0s The patch appears to include 1 new or modified test files. 0 mvndep 0m 10s Maven dependency ordering for branch +1 mvninstall 6m 59s trunk passed +1 compile 2m 26s trunk passed +1 checkstyle 0m 40s trunk passed +1 mvnsite 0m 56s trunk passed +1 mvneclipse 0m 28s trunk passed +1 findbugs 1m 29s trunk passed +1 javadoc 0m 42s trunk passed 0 mvndep 0m 10s Maven dependency ordering for patch +1 mvninstall 0m 46s the patch passed +1 compile 2m 23s the patch passed +1 javac 2m 23s the patch passed +1 checkstyle 0m 37s hadoop-yarn-project/hadoop-yarn: The patch generated 0 new + 83 unchanged - 4 fixed = 83 total (was 87) +1 mvnsite 0m 53s the patch passed +1 mvneclipse 0m 24s the patch passed +1 whitespace 0m 0s The patch has no whitespace issues. +1 findbugs 1m 43s the patch passed +1 javadoc 0m 39s the patch passed +1 unit 2m 16s hadoop-yarn-common in the patch passed. -1 unit 8m 17s hadoop-yarn-client in the patch failed. +1 asflicense 0m 17s The patch does not generate ASF License warnings. 33m 21s Reason Tests Failed junit tests hadoop.yarn.client.api.impl.TestYarnClient Subsystem Report/Notes Docker Image:yetus/hadoop:9560f25 JIRA Patch URL https://issues.apache.org/jira/secure/attachment/12818654/YARN-5213.2.patch JIRA Issue YARN-5213 Optional Tests asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle uname Linux 877271c769fe 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Build tool maven Personality /testptch/hadoop/patchprocess/precommit/personality/provided.sh git revision trunk / 92fe2db Default Java 1.8.0_91 findbugs v3.0.0 unit https://builds.apache.org/job/PreCommit-YARN-Build/12361/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt unit test logs https://builds.apache.org/job/PreCommit-YARN-Build/12361/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt Test Results https://builds.apache.org/job/PreCommit-YARN-Build/12361/testReport/ modules C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client U: hadoop-yarn-project/hadoop-yarn Console output https://builds.apache.org/job/PreCommit-YARN-Build/12361/console Powered by Apache Yetus 0.3.0 http://yetus.apache.org This message was automatically generated.
        Hide
        djp Junping Du added a comment -

        The test failure is not related. +1. Latest patch LGTM.
        Rohith Sharma K S, I will commit it tomorrow if you don't have further comments.

        Show
        djp Junping Du added a comment - The test failure is not related. +1. Latest patch LGTM. Rohith Sharma K S , I will commit it tomorrow if you don't have further comments.
        Hide
        rohithsharma Rohith Sharma K S added a comment -

        +1 LGTM

        Show
        rohithsharma Rohith Sharma K S added a comment - +1 LGTM
        Hide
        djp Junping Du added a comment -

        I have commit the patch to trunk and branch-2. Thanks Xuan Gong for patch contribution and Rohith Sharma K S for review and comments!

        Show
        djp Junping Du added a comment - I have commit the patch to trunk and branch-2. Thanks Xuan Gong for patch contribution and Rohith Sharma K S for review and comments!
        Hide
        hudson Hudson added a comment -

        SUCCESS: Integrated in Hadoop-trunk-Commit #10118 (See https://builds.apache.org/job/Hadoop-trunk-Commit/10118/)
        YARN-5213. Fix a bug in LogCLIHelpers which cause (junping_du: rev dc2f4b6ac8a6f8848457046cf9e1362d8f48495d)

        • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestLogsCLI.java
        • hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/LogCLIHelpers.java
        Show
        hudson Hudson added a comment - SUCCESS: Integrated in Hadoop-trunk-Commit #10118 (See https://builds.apache.org/job/Hadoop-trunk-Commit/10118/ ) YARN-5213 . Fix a bug in LogCLIHelpers which cause (junping_du: rev dc2f4b6ac8a6f8848457046cf9e1362d8f48495d) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestLogsCLI.java hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/LogCLIHelpers.java

          People

          • Assignee:
            xgong Xuan Gong
            Reporter:
            rohithsharma Rohith Sharma K S
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development