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

Craig Condit updated YUNIKORN-2289:
-----------------------------------
    Summary: Isolate e2e tests in separate namespaces  (was: Make e2e test run 
in separate namespace)

> Isolate e2e tests in separate namespaces
> ----------------------------------------
>
>                 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: Rajesh Kanhaiya Lal
>            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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to