You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Manikandan R (Jira)" <ji...@apache.org> on 2021/11/05 13:21:00 UTC
[jira] [Updated] (YUNIKORN-935) Refactor resourcemanagercallback
mock class
[ https://issues.apache.org/jira/browse/YUNIKORN-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikandan R updated YUNIKORN-935:
----------------------------------
Parent: YUNIKORN-337
Issue Type: Sub-task (was: Task)
> Refactor resourcemanagercallback mock class
> -------------------------------------------
>
> Key: YUNIKORN-935
> URL: https://issues.apache.org/jira/browse/YUNIKORN-935
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: scheduler-core
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
>
> Some test classes in core depending on rmcallback mocks ended up in having redundant mocks/code as part of moving plugin interfaces from core to SI (please refer https://issues.apache.org/jira/browse/YUNIKORN-907 for more details)
> This redundancy should be avoided by creating resuable common mockup classes.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org