[
https://issues.apache.org/jira/browse/YARN-7645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314009#comment-16314009
]
Hudson commented on YARN-7645:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13455 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13455/])
YARN-7645. (rkanter: rev 2aa4f0a55936239d35babd84da2a0d1a261bc9bd)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockRM.java
> TestContainerResourceUsage#testUsageAfterAMRestartWithMultipleContainers is
> flakey with FairScheduler
> -----------------------------------------------------------------------------------------------------
>
> Key: YARN-7645
> URL: https://issues.apache.org/jira/browse/YARN-7645
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: 3.1.0
>
> Attachments: YARN-7645.001.patch
>
>
> We've noticed some flakiness in
> {{TestContainerResourceUsage#testUsageAfterAMRestartWithMultipleContainers}}
> when using {{FairScheduler}}:
> {noformat}
> java.lang.AssertionError: Attempt state is not correct (timeout).
> expected:<ALLOCATED> but was:<SCHEDULED>
> at
> org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.amRestartTests(TestContainerResourceUsage.java:275)
> at
> org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartWithMultipleContainers(TestContainerResourceUsage.java:254)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
