[
https://issues.apache.org/jira/browse/YUNIKORN-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit updated YUNIKORN-293:
----------------------------------
Target Version: 0.12 (was: 0.11)
> mock core scheduler interactions for shim unit tests
> ----------------------------------------------------
>
> Key: YUNIKORN-293
> URL: https://issues.apache.org/jira/browse/YUNIKORN-293
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes, test - unit
> Affects Versions: 0.9
> Reporter: Wilfred Spiegelenburg
> Assignee: Minni Mittal
> Priority: Blocker
> Labels: newbie
>
> In the shim unit tests we start a full core scheduler. This leads to issues
> as when the full core is started we expect that there is a full working K8s
> cluster underneath.
> This is not the case and should not be the case for the unit tests. We need
> to mock the core scheduler instead of starting the full scheduler. There
> should be no need for build in workaround by placing code in "if test skip
> this part".
> The code should be robust enough to either handle the {{nil}} values that
> occur in tests or we need to return "empty" values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
