You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/09/10 21:58:00 UTC

[jira] [Resolved] (YUNIKORN-2289) Make e2e test run in separate namespace

     [ https://issues.apache.org/jira/browse/YUNIKORN-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Condit resolved YUNIKORN-2289.
------------------------------------
     Fix Version/s: 1.6.0
    Target Version: 1.6.0
        Resolution: Fixed

Merged to master.

> Make e2e test run in separate namespace
> ---------------------------------------
>
>                 Key: YUNIKORN-2289
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2289
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: test - e2e
>            Reporter: Kuan Po Tseng
>            Assignee: JiaChi Wang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>
> as  Peter Bacsko mentioned in https://issues.apache.org/jira/browse/YUNIKORN-2247
> {quote}
> During the review of PR #705, we realized that preemption test cases are not separated by namespaces. This is bad practice because test can easily interfere with each other, leading to suble, hard-to-debug problems.
> {quote}
> Currently there are some e2e tests still share the same namesapce e.g. basic_scheduling_test, persistent_volume, ... and so on.
> IMO we should align the behavior, make sure all e2e test run in separate namespace.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org