Hadoop-Mapreduce-trunk - Build # 1160 - Still Failing
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1160/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 31005 lines...] Results : Failed tests: testForEmptyFile(org.apache.hadoop.mapreduce.lib.input.TestCombineFileInputFormat): expected:0 but was:1 Tests run: 384, Failures: 1, Errors: 0, Skipped: 14 [INFO] [INFO] Reactor Summary: [INFO] [INFO] hadoop-yarn ... SUCCESS [1.800s] [INFO] hadoop-yarn-api ... SUCCESS [7.849s] [INFO] hadoop-yarn-common SUCCESS [29.920s] [INFO] hadoop-yarn-server SUCCESS [0.112s] [INFO] hadoop-yarn-server-common . SUCCESS [2.602s] [INFO] hadoop-yarn-server-nodemanager SUCCESS [2:23.637s] [INFO] hadoop-yarn-server-web-proxy .. SUCCESS [1.229s] [INFO] hadoop-yarn-server-resourcemanager SUCCESS [3:33.466s] [INFO] hadoop-yarn-server-tests .. SUCCESS [40.789s] [INFO] hadoop-mapreduce-client ... SUCCESS [0.064s] [INFO] hadoop-mapreduce-client-core .. SUCCESS [1:13.762s] [INFO] hadoop-yarn-applications .. SUCCESS [0.090s] [INFO] hadoop-yarn-applications-distributedshell . SUCCESS [12.265s] [INFO] hadoop-yarn-applications-unmanaged-am-launcher SUCCESS [9.876s] [INFO] hadoop-yarn-site .. SUCCESS [0.150s] [INFO] hadoop-mapreduce-client-common SUCCESS [18.787s] [INFO] hadoop-mapreduce-client-shuffle ... SUCCESS [0.986s] [INFO] hadoop-mapreduce-client-app ... SUCCESS [4:28.346s] [INFO] hadoop-mapreduce-client-hs SUCCESS [1:05.785s] [INFO] hadoop-mapreduce-client-jobclient . FAILURE [35:05.002s] [INFO] Apache Hadoop MapReduce Examples .. SKIPPED [INFO] hadoop-mapreduce .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 49:57.754s [INFO] Finished at: Tue Aug 07 14:12:07 UTC 2012 [INFO] Final Memory: 27M/442M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project hadoop-mapreduce-client-jobclient: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-trunk/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :hadoop-mapreduce-client-jobclient Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE Archiving artifacts Error updating JIRA issues. Saving issues for next build. JIRA is currently being reindexed. Depending on how large the database is, this may take a few minutes. Jira will automatically become available as soon as this task is complete. Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Created] (MAPREDUCE-4524) Capacity Scheduler does not support adding sub-queues to the existing queues.
Kiran BC created MAPREDUCE-4524: --- Summary: Capacity Scheduler does not support adding sub-queues to the existing queues. Key: MAPREDUCE-4524 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4524 Project: Hadoop Map/Reduce Issue Type: Bug Components: capacity-sched, documentation Affects Versions: 0.23.0 Reporter: Kiran BC In-line to the issue, MAPREDUCE-3410, there should be a note stating that - Capacity Scheduler does not support adding sub-queues to the existing queue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-3410) Capacity scheduler reconfiguration of queues does not work for add sub-queues to an existing queue
[ https://issues.apache.org/jira/browse/MAPREDUCE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved MAPREDUCE-3410. -- Resolution: Later For now we should punt on this - this is akin to 'delete queue' as Jason explained. Capacity scheduler reconfiguration of queues does not work for add sub-queues to an existing queue -- Key: MAPREDUCE-3410 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3410 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Anupam Seth If we have an existing queue configuration such as root |--- A |--- B and we attempt to reconfigure it so that we now have root |--- A |--- A1 |--- A2 |--- B we get an IOException as follows: java.io.IOException: Failed to re-init queues at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:197) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestLeafQueue.testInitializeQueue(TestLeafQueue.java:206) 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:45) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) 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 org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:78) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) Caused by: java.io.IOException: Trying to reinitialize root.a from root.a at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.reinitialize(LeafQueue.java:524) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.reinitialize(ParentQueue.java:360) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitializeQueues(CapacityScheduler.java:240) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:194) ... 32 more This is apparently because the CapacityScheduler still wants to think of A as a LeafQueue instead of realizing it to be updated as a ParentQueue. Maybe, this use case is not supposed to be supported, in which case, probably the documentation should be updated to state this scenario as such more clearly
