mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
7013b32d15
Currently the release test runner prefers the first successfully version of a cluster env, instead of the last version. But sometimes a cluster env may build successfully on Anyscale but cannot launch cluster successfully (e.g. version 2 here) or new dependencies need to be installed, so a new version needs to be built. The existing logic always picks up the 1st successful build and cannot pick up the new cluster env version. Although this is an edge case (tweaking cluster env versions, with the same Ray wheel or cluster env name), I believe it is possible for others to run into it. Also, avoid running most of the CI tests for changes under release/ray_release/. |
||
|---|---|---|
| .. | ||
| air_tests/horovod | ||
| benchmarks | ||
| golden_notebook_tests | ||
| jobs_tests | ||
| kubernetes_manual_tests | ||
| lightgbm_tests | ||
| long_running_distributed_tests | ||
| long_running_tests | ||
| microbenchmark | ||
| ml_user_tests | ||
| nightly_tests | ||
| ray_release | ||
| release_logs | ||
| rllib_tests | ||
| runtime_env_tests | ||
| serve_tests | ||
| train_tests/horovod | ||
| tune_tests | ||
| util | ||
| xgboost_tests | ||
| __init__.py | ||
| BUILD | ||
| README.md | ||
| release_tests.yaml | ||
| requirements.txt | ||
| requirements_buildkite.txt | ||
| run_release_test.sh | ||
| setup.py | ||
Release Tests
While the exact release process relies on Anyscale internal tooling, the tests we run during the releases are located at https://github.com/ray-project/ray/blob/master/release/.buildkite/build_pipeline.py