You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2021/12/20 07:30: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 ]
Wilfred Spiegelenburg updated YUNIKORN-935:
-------------------------------------------
Parent: YUNIKORN-983 (was: YUNIKORN-337)
> 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.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org