[
https://issues.apache.org/jira/browse/YARN-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215259#comment-16215259
]
Arun Suresh commented on YARN-7343:
-----------------------------------
Thanks for the extensive testing [~sampada15].
Wondering if it is possible to achieve the same functionality without using
powermock though. From a cursory scan of the patch, it looks like most of if
can be accomplished using plain mockito - except maybe some field
modifications. If that is the only use, then maybe we can change the visibility
of the field or add methods with {{VisibleForTesting}} annotations.
The reason I am pushing back on using powermock is that there has been a
discussion on the [mailing
list|http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201709.mbox/browser]
about using powermock and it is not going well :)
> Add a junit test for ContainerScheduler recovery
> ------------------------------------------------
>
> Key: YARN-7343
> URL: https://issues.apache.org/jira/browse/YARN-7343
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: kartheek muthyala
> Assignee: Sampada Dehankar
> Priority: Minor
> Attachments: YARN-7343.001.patch
>
>
> With queuing at NM, Container recovery becomes interesting. Add a junit test
> for recovering containers in different states. This should test the recovery
> with the ContainerScheduler class that was introduced for enabling container
> queuing on contention of resources.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
