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

Weiwei Yang updated YUNIKORN-744:
---------------------------------
    Description: 
We found a regression a while back: YUNIKORN-741. Such regression should be 
captured into our e2e tests. We need to add some coverage to make sure the 
restart is well covered. I think the general workflow can be:
 * start the scheduler
 * run some simple workloads
 * restart the scheduler
 * call the healthcheck REST APIĀ 

we can leverage the healthcheck API to verify the scheduler correctness, if 
necessary, we can also add some more verifications in the healthcheck endpoint.

  was:We found a regression a while back: YUNIKORN-741. Such regression should 
be captured into our e2e tests. We need to add some coverage to make sure the 
restart is well covered.


> Add scheduler restart coverage to e2e test
> ------------------------------------------
>
>                 Key: YUNIKORN-744
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-744
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: shim - kubernetes
>            Reporter: Weiwei Yang
>            Assignee: Ting Yao,Huang
>            Priority: Major
>             Fix For: 1.0.0
>
>
> We found a regression a while back: YUNIKORN-741. Such regression should be 
> captured into our e2e tests. We need to add some coverage to make sure the 
> restart is well covered. I think the general workflow can be:
>  * start the scheduler
>  * run some simple workloads
>  * restart the scheduler
>  * call the healthcheck REST APIĀ 
> we can leverage the healthcheck API to verify the scheduler correctness, if 
> necessary, we can also add some more verifications in the healthcheck 
> endpoint.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to