You are viewing a plain text version of this content. The canonical link for it is here.

Posted to reviews@yunikorn.apache.org by GitBox <gi...@apache.org> on 2022/02/26 04:28:00 UTC

[GitHub] [incubator-yunikorn-k8shim] ronazhan commented on pull request #369: [YUNIKORN-1040] add e2e test that re-starts the scheduler pod

ronazhan commented on pull request #369:
URL: https://github.com/apache/incubator-yunikorn-k8shim/pull/369#issuecomment-1051566558


   Yes, @wilfred-s and @yangwwei are right that the port-forward connection needs to be restarted as well after the new scheduler pod is brought up. I don't believe that port-forward is available using the k8s go-client library, so this might have to be done as a shell command
   
   I haven't looked much into the ginkgo v2 changes, but the recovery suite can be separated by using `--skip-package`  flag. Then, it can be run separately than the other test packages
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@yunikorn.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org