mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
Add K8s test to release process (#13694)
This commit is contained in:
parent
8b8d6b984b
commit
fe8262afd0
2 changed files with 9 additions and 2 deletions
|
@ -56,6 +56,10 @@ This checklist is meant to be used in conjunction with the RELEASE_PROCESS.rst d
|
|||
- [ ] Results added to `release/release_logs`
|
||||
- [ ] stress_tests
|
||||
- [ ] unit_gpu_tests
|
||||
- [ ] ASAN Test
|
||||
- [ ] K8s Test
|
||||
- [ ] K8s cluster launcher test
|
||||
- [ ] K8s operator test
|
||||
|
||||
## Final Steps
|
||||
- [ ] Wheels uploaded to Test PyPI
|
||||
|
|
|
@ -136,8 +136,11 @@ is generally the easiest way to run release tests.
|
|||
|
||||
5. **ASAN tests**
|
||||
|
||||
Run the ``ci/asan_tests`` with the commit. This will enable ASAN build and run the
|
||||
whole Python tests to detect memory leaks.
|
||||
Run the ``ci/asan_tests`` with the commit. This will enable ASAN build and run the whole Python tests to detect memory leaks.
|
||||
|
||||
6. **K8s operator tests**
|
||||
|
||||
Run the ``python/ray/tests/test_k8s_*`` to make sure K8s cluster launcher and operator works. Make sure the docker image is the released version.
|
||||
|
||||
Identify and Resolve Release Blockers
|
||||
-------------------------------------
|
||||
|
|
Loading…
Add table
Reference in a new issue