[
https://issues.apache.org/jira/browse/YARN-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369160#comment-15369160
]
Varun Saxena commented on YARN-5318:
------------------------------------
bq. not related to this patch, I was thinking a more general way to handle test
failure, some failure are caused by scheduler event processed async, If we had
to way to drain all RM events and scheduler event, I may help to reduce the
test fail change.
Agree. It would be useful to have a mechanism to drain scheduler event queue as
well. It would be better than having deterministic sleeps in tests.
There will be several tests where we will be checking state of the scheduler
after dispatching an event which would then generate a scheduler event.
> TestRMAdminService#testRefreshNodesResourceWithFileSystemBasedConfigurationProvider
> fails intermittently.
> ---------------------------------------------------------------------------------------------------------
>
> Key: YARN-5318
> URL: https://issues.apache.org/jira/browse/YARN-5318
> Project: Hadoop YARN
> Issue Type: Test
> Reporter: sandflee
> Assignee: Jun Gong
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: YARN-5318.01.patch
>
>
> org.junit.ComparisonFailure: expected:<<memory:[4096, vCores:4]>> but
> was:<<memory:[5120, vCores:5]>>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.hadoop.yarn.server.resourcemanager.TestRMAdminService.testRefreshNodesResourceWithFileSystemBasedConfigurationProvider(TestRMAdminService.java:238)
> https://builds.apache.org/job/PreCommit-YARN-Build/12204/testReport/org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager/TestAMRestart/testAMRestartNotLostContainerCompleteMsg/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
