hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-260) YARN tests have multiple failures on Windows due to "Queue configuration missing"
Date Wed, 05 Dec 2012 18:41:57 GMT

    [ 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.<init>(MiniMRCluster.java:180)
	at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:170)
	at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:162)
	at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:154)
	at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:147)
	at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:140)
	at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:133)
	at org.apache.hadoop.mapred.MiniMRCluster.<init>(MiniMRCluster.java:128)
	at org.apache.hadoop.streaming.TestFileArgs.<init>(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

Mime
View raw message