[
https://issues.apache.org/jira/browse/YARN-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278276#comment-14278276
]
Jian He commented on YARN-3064:
-------------------------------
caused by YARN-3019. Some tests are still based on the non-work-preserving
recovery mechanism
Uploaded a patch to fix the tests.
> TestRMRestart/TestContainerResourceUsage/TestNodeManagerResync failure with
> allocation timeout in trunk
> -------------------------------------------------------------------------------------------------------
>
> Key: YARN-3064
> URL: https://issues.apache.org/jira/browse/YARN-3064
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Reporter: Wangda Tan
> Assignee: Jian He
> Priority: Critical
> Attachments: YARN-3064.1.patch
>
>
> Noticed consistent tests failure, see:
> https://builds.apache.org/job/PreCommit-YARN-Build/6332//testReport/
> Logs like:
> {code}
> Error Message
> Attempt state is not correct (timedout) expected:<ALLOCATED> but
> was:<SCHEDULED>
> Stacktrace
> java.lang.AssertionError: Attempt state is not correct (timedout)
> expected:<ALLOCATED> but was:<SCHEDULED>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at
> org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:152)
> at
> org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testQueueMetricsOnRMRestart(TestRMRestart.java:1794)
> {code}
> I can reproduce it in local environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
