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

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

IIUC NodeLabelsUpdateSchedulerEvent.NODE_LABELS_UPDATE event is yet to be 
processed. We are waiting for only node to be added not for completion of event 
processing.
{noformat}
    rm.registerNode("h4:1234", 10 * GB); // label = <empty>    
    waitSchedulerNodeJoined(rm, 4);
{noformat}
This could be the cause for random failures


> Unit test intermittent failure: 
> TestNodeLabelContainerAllocation#testQueueUsedCapacitiesUpdate
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-4890
>                 URL: https://issues.apache.org/jira/browse/YARN-4890
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>
> Message:
> {code}
> Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 314.062 sec 
> <<< FAILURE! - in 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestNodeLabelContainerAllocation
> testQueueUsedCapacitiesUpdate(org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestNodeLabelContainerAllocation)
>   Time elapsed: 12.426 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<0.3> but was:<0.6>
>       at org.junit.Assert.fail(Assert.java:88)
>       at org.junit.Assert.failNotEquals(Assert.java:743)
>       at org.junit.Assert.assertEquals(Assert.java:519)
>       at org.junit.Assert.assertEquals(Assert.java:609)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestNodeLabelContainerAllocation.checkQueueUsedCapacity(TestNodeLabelContainerAllocation.java:1163)
>       at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestNodeLabelContainerAllocation.testQueueUsedCapacitiesUpdate(TestNodeLabelContainerAllocation.java:1382)
> {code}



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

Reply via email to