Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 39749D740 for ; Wed, 5 Dec 2012 18:41:58 +0000 (UTC) Received: (qmail 71515 invoked by uid 500); 5 Dec 2012 18:41:58 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 71489 invoked by uid 500); 5 Dec 2012 18:41:58 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 71478 invoked by uid 99); 5 Dec 2012 18:41:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 18:41:58 +0000 Date: Wed, 5 Dec 2012 18:41:57 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: <668396863.64288.1354732918121.JavaMail.jiratomcat@arcas> In-Reply-To: <788435675.64271.1354732678352.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (YARN-260) YARN tests have multiple failures on Windows due to "Queue configuration missing" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510668#comment-13510668 ] Chris Nauroth commented on YARN-260: ------------------------------------ There are 6 test suites failing on Windows due to this problem. It looks like they are all in streaming. I believe some similar issues were solved on trunk recently, so we may want to review that. {code} testCommandLine(org.apache.hadoop.streaming.TestFileArgs) Time elapsed: 13407 sec <<< ERROR! org.apache.hadoop.yarn.YarnException: Failed to Start org.apache.hadoop.mapred.MiniMRCluster at org.apache.hadoop.yarn.service.CompositeService.start(CompositeService.java:78) at org.apache.hadoop.mapred.MiniMRClientClusterFactory.create(MiniMRClientClusterFactory.java:71) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:180) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:170) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:162) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:154) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:147) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:140) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:133) at org.apache.hadoop.mapred.MiniMRCluster.(MiniMRCluster.java:128) at org.apache.hadoop.streaming.TestFileArgs.(TestFileArgs.java:57) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:209) at org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:258) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:255) 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.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) 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: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: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) Caused by: org.apache.hadoop.yarn.YarnException: java.lang.IllegalStateException: Queue configuration missing child queue names for root at org.apache.hadoop.yarn.server.MiniYARNCluster$ResourceManagerWrapper.start(MiniYARNCluster.java:184) at org.apache.hadoop.yarn.service.CompositeService.start(CompositeService.java:68) ... 39 more Caused by: java.lang.IllegalStateException: Queue configuration missing child queue names for root at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:303) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:228) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:198) at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.init(ResourceManager.java:201) at org.apache.hadoop.yarn.server.MiniYARNCluster$ResourceManagerWrapper.start(MiniYARNCluster.java:164) ... 40 more {code} > YARN tests have multiple failures on Windows due to "Queue configuration missing" > --------------------------------------------------------------------------------- > > Key: YARN-260 > URL: https://issues.apache.org/jira/browse/YARN-260 > Project: Hadoop YARN > Issue Type: Bug > Components: applications > Affects Versions: trunk-win > Reporter: Chris Nauroth > Assignee: Chris Nauroth > > There are multiple test failures due to "Queue configuration missing child queue names for root". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira