mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
![]() Adds a unit-tested and restructured ray_release package for running release tests. Relevant changes in behavior: Per default, Buildkite will wait for the wheels of the current commit to be available. Alternatively, users can a) specify a different commit hash, b) a wheels URL (which we will also wait for to be available) or c) specify a branch (or user/branch combination), in which case the latest available wheels will be used (e.g. if master is passed, behavior matches old default behavior). The main subpackages are: Cluster manager: Creates cluster envs/computes, starts cluster, terminates cluster Command runner: Runs commands, e.g. as client command or sdk command File manager: Uploads/downloads files to/from session Reporter: Reports results (e.g. to database) Much of the code base is unit tested, but there are probably some pieces missing. Example build (waited for wheels to be built): https://buildkite.com/ray-project/kf-dev/builds/51#_ Wheel build: https://buildkite.com/ray-project/ray-builders-branch/builds/6023 |
||
---|---|---|
.. | ||
.buildkite | ||
alerts | ||
golden_notebook_tests | ||
horovod_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 | ||
sgd_tests | ||
tune_tests | ||
util | ||
xgboost_tests | ||
__init__.py | ||
alert.py | ||
BUILD | ||
config_generator.html | ||
e2e.py | ||
README.md | ||
release_tests.yaml | ||
requirements.txt | ||
requirements_buildkite.txt | ||
run_e2e.sh | ||
run_release_test.sh | ||
setup.py | ||
test_owners.yaml |
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