[ 
https://issues.apache.org/jira/browse/YARN-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744421#comment-15744421
 ] 

Bibin A Chundatt commented on YARN-5994:
----------------------------------------

[~ebadger]
As [~sunilg] mentioned app shouldnt be null after submit. As part of YARN-5773 
only change is node addition and the events should have got drained.
To recheck the issue tried running locally on *trunk*  about 50-70 times. Didnt 
encounter the issue.
{noformat}
for i in {1..100}; do mvn test -Dtest=TestCapacityScheduler#testAMLimitUsage | 
grep BUILD; done
{noformat}
Could you please upload the logs.
Was the test failure on trunk ?

> TestCapacityScheduler.testAMLimitUsage fails intermittently
> -----------------------------------------------------------
>
>                 Key: YARN-5994
>                 URL: https://issues.apache.org/jira/browse/YARN-5994
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Eric Badger
>            Assignee: Eric Badger
>
> {noformat}
> java.lang.AssertionError: app shouldn't be null
>       at org.junit.Assert.fail(Assert.java:88)
>       at org.junit.Assert.assertTrue(Assert.java:41)
>       at org.junit.Assert.assertNotNull(Assert.java:621)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:169)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:577)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:488)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:395)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler.verifyAMLimitForLeafQueue(TestCapacityScheduler.java:3389)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler.testAMLimitUsage(TestCapacityScheduler.java:3251)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to