[ https://issues.apache.org/jira/browse/YARN-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941751#comment-13941751 ]
Karthik Kambatla commented on YARN-1854: ---------------------------------------- For races like this, where we might be trying to verify something too soon, it should be okay to verify after waiting for a little bit. May be, sleeping for small intervals - 100 ms - in a loop until the state is correct sounds reasonable to me. > TestRMHA#testStartAndTransitions Fails > -------------------------------------- > > Key: YARN-1854 > URL: https://issues.apache.org/jira/browse/YARN-1854 > Project: Hadoop YARN > Issue Type: Test > Affects Versions: 2.4.0 > Reporter: Mit Desai > Assignee: Rohith > Priority: Blocker > Attachments: YARN-1854.patch > > > {noformat} > testStartAndTransitions(org.apache.hadoop.yarn.server.resourcemanager.TestRMHA) > Time elapsed: 5.883 sec <<< FAILURE! > java.lang.AssertionError: Incorrect value for metric availableMB > expected:<2048> but was:<4096> > at org.junit.Assert.fail(Assert.java:93) > at org.junit.Assert.failNotEquals(Assert.java:647) > at org.junit.Assert.assertEquals(Assert.java:128) > at org.junit.Assert.assertEquals(Assert.java:472) > at > org.apache.hadoop.yarn.server.resourcemanager.TestRMHA.assertMetric(TestRMHA.java:396) > at > org.apache.hadoop.yarn.server.resourcemanager.TestRMHA.verifyClusterMetrics(TestRMHA.java:387) > at > org.apache.hadoop.yarn.server.resourcemanager.TestRMHA.testStartAndTransitions(TestRMHA.java:160) > Results : > Failed tests: > > TestRMHA.testStartAndTransitions:160->verifyClusterMetrics:387->assertMetric:396 > Incorrect value for metric availableMB expected:<2048> but was:<4096> > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)