Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-5688

TestStagingCleanup fails intermittently with JDK7

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0, 2.3.0
    • Fix Version/s: 3.0.0, 2.4.0
    • Component/s: None
    • Labels:
    • Hadoop Flags:
      Reviewed

      Description

      Due to random ordering ordering in JDK7, the test TestStagingCleanup#testDeletionofStagingOnKillLastTry is failing

      Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.231 sec <<< FAILURE!
      test(org.apache.hadoop.mapreduce.v2.app.TestStagingCleanup)  Time elapsed: 3882 sec  <<< ERROR!
      java.lang.NullPointerException
      	at org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler.serviceStop(JobHistoryEventHandler.java:349)
      	at org.apache.hadoop.service.AbstractService.stop(AbstractService.java:221)
      	at org.apache.hadoop.service.ServiceOperations.stop(ServiceOperations.java:52)
      	at org.apache.hadoop.service.ServiceOperations.stopQuietly(ServiceOperations.java:80)
      	at org.apache.hadoop.service.CompositeService.stop(CompositeService.java:159)
      	at org.apache.hadoop.service.CompositeService.serviceStop(CompositeService.java:132)
      	at org.apache.hadoop.service.AbstractService.stop(AbstractService.java:221)
      	at org.apache.hadoop.mapreduce.v2.app.MRAppMaster$MRAppMasterShutdownHook.run(MRAppMaster.java:1399)
      	at org.apache.hadoop.mapreduce.v2.app.TestStagingCleanup.testDeletionofStagingOnKillLastTry(TestStagingCleanup.java:239)
      	at org.apache.hadoop.mapreduce.v2.app.TestStagingCleanup.test(TestStagingCleanup.java:82)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:606)
      	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.junit4.JUnit4Provider.execute(JUnit4Provider.java:242)
      	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137)
      	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:606)
      	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
      	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
      	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
      	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
      	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
      
      1. MAPREDUCE-5688.patch
        0.9 kB
        Mit Desai
      2. MAPREDUCE-5688-v2.patch
        3 kB
        Mit Desai
      3. MAPREDUCE-5688-v2.patch
        3 kB
        Mit Desai

        Activity

        Hide
        Mit Desai added a comment -

        I am looking into the issue. Will be posting the patch soon.

        Show
        Mit Desai added a comment - I am looking into the issue. Will be posting the patch soon.
        Hide
        Mit Desai added a comment -

        patch attached for trunk and branch2

        Show
        Mit Desai added a comment - patch attached for trunk and branch2
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12625107/MAPREDUCE-5688.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app:

        org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4336//testReport/
        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4336//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12625107/MAPREDUCE-5688.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. -1 core tests . The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app: org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4336//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4336//console This message is automatically generated.
        Hide
        Mit Desai added a comment -

        TestRMContainerAllocator does not fail due to this patch.
        Just to double check, I ran the TestRMContainerAllocator test with and without the patch and I found that the test fails in both cases.

        Show
        Mit Desai added a comment - TestRMContainerAllocator does not fail due to this patch. Just to double check, I ran the TestRMContainerAllocator test with and without the patch and I found that the test fails in both cases.
        Hide
        Jonathan Eagles added a comment -

        Mit, thanks for the patch. Couple of minor nits.

        • Re-title this jira since this is not a test problem according to the patch, but a race condition in the MRAppMaster that is exposed most frequently via this test.
        • Add your analysis to the jira so that the actual problem is documented and captured for future use.
        • Please determine if the java7 label is still accurate based on your analysis
        Show
        Jonathan Eagles added a comment - Mit, thanks for the patch. Couple of minor nits. Re-title this jira since this is not a test problem according to the patch, but a race condition in the MRAppMaster that is exposed most frequently via this test. Add your analysis to the jira so that the actual problem is documented and captured for future use. Please determine if the java7 label is still accurate based on your analysis
        Hide
        Mit Desai added a comment -

        Thanks Jon for the Review!

        Re-title this jira since this is not a test problem according to the patch, but a race condition in the MRAppMaster that is exposed most frequently via this test.

        I have renamed this JIRA accordingly. I would like to make one clarification here. I do not see this problem as a race. The bug is exposed by this test running with JDK7 and its random ordering.

        Add your analysis to the jira so that the actual problem is documented and captured for future use.

        This failure is intermittent. It is only caused when the test TestStagingCleanup runs in a particular order. For example, testDeletionofStagingOnReboot() followed by testDeletionofStagingOnKillLastTry()

        The reason for the failure is due to the notifyIsLastAMRetry(). When this function is called, it calls setForcejobCompletion(). If the appMaster.stop() is called after the setForcejobCompletion(), it tries to stop the appMaster which was already forced to stop. As a result, it gets an NPE trying to stop the appMaster. If the appMaster.stop() is called in the first place, we won't get the NPE when it tries forceJobCompletion as there already is a null check before it proceeds.

        hook.run() is also called in testDeletionofStagingOnKill(). But we do not get the NPE in that case. The reason for this is, in this test, we have 4 app attempts. MRAppMaster appMaster = new TestMRApp(attemptId, mockAlloc, 4);
        where as in testDeletionofStagingOnKillLastTry() we have only 1 attempt to make sure there is no retry. MRAppMaster appMaster = new TestMRApp(attemptId, mockAlloc, 1); //no retry

        Please determine if the java7 label is still accurate based on your analysis

        We still need the java7 label as the TestStagingCleanup will not always fail without this fix. It only fails when the tests run in a particular order.

        Show
        Mit Desai added a comment - Thanks Jon for the Review! Re-title this jira since this is not a test problem according to the patch, but a race condition in the MRAppMaster that is exposed most frequently via this test. I have renamed this JIRA accordingly. I would like to make one clarification here. I do not see this problem as a race. The bug is exposed by this test running with JDK7 and its random ordering. Add your analysis to the jira so that the actual problem is documented and captured for future use. This failure is intermittent. It is only caused when the test TestStagingCleanup runs in a particular order. For example, testDeletionofStagingOnReboot() followed by testDeletionofStagingOnKillLastTry() The reason for the failure is due to the notifyIsLastAMRetry(). When this function is called, it calls setForcejobCompletion(). If the appMaster.stop() is called after the setForcejobCompletion(), it tries to stop the appMaster which was already forced to stop. As a result, it gets an NPE trying to stop the appMaster. If the appMaster.stop() is called in the first place, we won't get the NPE when it tries forceJobCompletion as there already is a null check before it proceeds. hook.run() is also called in testDeletionofStagingOnKill(). But we do not get the NPE in that case. The reason for this is, in this test, we have 4 app attempts. MRAppMaster appMaster = new TestMRApp(attemptId, mockAlloc, 4); where as in testDeletionofStagingOnKillLastTry() we have only 1 attempt to make sure there is no retry. MRAppMaster appMaster = new TestMRApp(attemptId, mockAlloc, 1); //no retry Please determine if the java7 label is still accurate based on your analysis We still need the java7 label as the TestStagingCleanup will not always fail without this fix. It only fails when the tests run in a particular order.
        Hide
        Chen He added a comment -

        Thank you Mit.
        +1 patch is good.
        It will be great if you submit an updated version and get +1 from Hadoop QA.

        Show
        Chen He added a comment - Thank you Mit. +1 patch is good. It will be great if you submit an updated version and get +1 from Hadoop QA.
        Hide
        Mit Desai added a comment -

        Thanks for the inputs, Chen He.
        The failure of TestRMContainerAllocator is due to MAPREDUCE-5743 which was fixed a day ago.

        I think the same patch will be good to go. I have resubmitted it so that I get the HadoopQA comment again. And I think it will pass this time.

        Show
        Mit Desai added a comment - Thanks for the inputs, Chen He . The failure of TestRMContainerAllocator is due to MAPREDUCE-5743 which was fixed a day ago. I think the same patch will be good to go. I have resubmitted it so that I get the HadoopQA comment again. And I think it will pass this time.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12625107/MAPREDUCE-5688.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. There were no new javadoc warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4350//testReport/
        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4350//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12625107/MAPREDUCE-5688.patch against trunk revision . +1 @author . The patch does not contain any @author tags. -1 tests included . The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4350//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4350//console This message is automatically generated.
        Hide
        Mit Desai added a comment -

        The test failure is due to the improper design in MRAppMaster. There will be no test changes for this JIRA

        Show
        Mit Desai added a comment - The test failure is due to the improper design in MRAppMaster. There will be no test changes for this JIRA
        Hide
        Mit Desai added a comment -

        Attaching a new patch.

        Show
        Mit Desai added a comment - Attaching a new patch.
        Hide
        Mit Desai added a comment -

        Jon, I looked in the issue further more and found that there should not be a problem with MRAppMaster. It is a test issue and I have uploaded the patch that reflect it.

        Show
        Mit Desai added a comment - Jon, I looked in the issue further more and found that there should not be a problem with MRAppMaster. It is a test issue and I have uploaded the patch that reflect it.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12630317/MAPREDUCE-5688-v2.patch
        against trunk revision .

        -1 patch. The patch command could not apply the patch.

        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4364//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12630317/MAPREDUCE-5688-v2.patch against trunk revision . -1 patch . The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4364//console This message is automatically generated.
        Hide
        Mit Desai added a comment -

        Reattaching the patch.

        Show
        Mit Desai added a comment - Reattaching the patch.
        Hide
        Mit Desai added a comment -

        Problems

        1. The test testDeletionofStagingOnKillLastTry runs fine if it was run individually or when it runs after testDeletionofStagingOnKill or testNoDeletionofStaginigOnReboot.
        2. The test fails only when it runs after testDeletionofStagingOnReboot, testDeletionofStagingOnUnregisteredFailure and testDeletionofStaging
        3. When I ran the tests testDeletionofStagingOnReboot, testDeletionofStagingOnUnregisteredFailure and testDeletionofStaging individually, they passes. But on looking the logs, I found that these tests passed even though NPEs were reported during their execution. I think that the testDeletionofStagingOnKillLastTry fails because of these NPEs.

        Cause
        There are two causes for the NPEs that come up in the test.

        1. The attemptId in testDeletionofStaging starts with 0. When test proceeds it decrements the value by 1 and ends up with attemptId=-1. Cause for one of the NPE.
        2. The JobHistoryEventHandler will throw an NPE when setSummarySlotSeconds tries to access the counters as there will be no reference to it.
        Show
        Mit Desai added a comment - Problems The test testDeletionofStagingOnKillLastTry runs fine if it was run individually or when it runs after testDeletionofStagingOnKill or testNoDeletionofStaginigOnReboot . The test fails only when it runs after testDeletionofStagingOnReboot , testDeletionofStagingOnUnregisteredFailure and testDeletionofStaging When I ran the tests testDeletionofStagingOnReboot , testDeletionofStagingOnUnregisteredFailure and testDeletionofStaging individually, they passes. But on looking the logs, I found that these tests passed even though NPEs were reported during their execution. I think that the testDeletionofStagingOnKillLastTry fails because of these NPEs. Cause There are two causes for the NPEs that come up in the test. The attemptId in testDeletionofStaging starts with 0. When test proceeds it decrements the value by 1 and ends up with attemptId=-1. Cause for one of the NPE. The JobHistoryEventHandler will throw an NPE when setSummarySlotSeconds tries to access the counters as there will be no reference to it.
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12630321/MAPREDUCE-5688-v2.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. There were no new javadoc warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4365//testReport/
        Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4365//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12630321/MAPREDUCE-5688-v2.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4365//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4365//console This message is automatically generated.
        Hide
        Hudson added a comment -

        SUCCESS: Integrated in Hadoop-trunk-Commit #5205 (See https://builds.apache.org/job/Hadoop-trunk-Commit/5205/)
        MAPREDUCE-5688. TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631)

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Show
        Hudson added a comment - SUCCESS: Integrated in Hadoop-trunk-Commit #5205 (See https://builds.apache.org/job/Hadoop-trunk-Commit/5205/ ) MAPREDUCE-5688 . TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631 ) /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Hide
        Hudson added a comment -

        SUCCESS: Integrated in Hadoop-Yarn-trunk #489 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/489/)
        MAPREDUCE-5688. TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631)

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Show
        Hudson added a comment - SUCCESS: Integrated in Hadoop-Yarn-trunk #489 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/489/ ) MAPREDUCE-5688 . TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631 ) /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Hide
        Hudson added a comment -

        FAILURE: Integrated in Hadoop-Hdfs-trunk #1681 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1681/)
        MAPREDUCE-5688. TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631)

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Show
        Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk #1681 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1681/ ) MAPREDUCE-5688 . TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631 ) /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Hide
        Hudson added a comment -

        SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1706 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1706/)
        MAPREDUCE-5688. TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631)

        • /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
        • /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Show
        Hudson added a comment - SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1706 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1706/ ) MAPREDUCE-5688 . TestStagingCleanup fails intermittently with JDK7 (Mit Desai via jeagles) (jeagles: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570631 ) /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestStagingCleanup.java
        Hide
        Jason Lowe added a comment -

        I pulled this into branch-2.4 as well.

        Show
        Jason Lowe added a comment - I pulled this into branch-2.4 as well.

          People

          • Assignee:
            Mit Desai
            Reporter:
            Mit Desai
          • Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development