[jira] [Resolved] (YUNIKORN-1404) e2e: don't delete individual pods when jobs are submitted

["Craig Condit (Jira)" <ji...@apache.org>]

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

Craig Condit resolved YUNIKORN-1404.
------------------------------------
     Fix Version/s: 1.3.0
    Target Version: 1.3.0
        Resolution: Fixed

Merged to master.

> e2e: don't delete individual pods when jobs are submitted
> ---------------------------------------------------------
>
>                 Key: YUNIKORN-1404
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1404
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: test - e2e
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.3.0
>
>
> In certain tests, we submit a sleep job and at the end of the execution, we delete the pods in a loop to clean up.
> However, if a pod is deleted, a new one is created immediately. We should delete the job first, then proceed to the jobs to clean up quickly (similar to how we clean up in admission controller tests).



--
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