You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Sunil G (Jira)" <ji...@apache.org> on 2021/09/21 02:10:00 UTC
[jira] [Updated] (YUNIKORN-293) mock core scheduler interactions
for shim unit tests
[ https://issues.apache.org/jira/browse/YUNIKORN-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil G updated YUNIKORN-293:
-----------------------------
Labels: newbie (was: )
> 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
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org