mirror of
https://github.com/vale981/ray
synced 2025-03-06 10:31:39 -05:00
1ed8bd0345
This line: ``` pip3 install -U --force-reinstall xgboost xgboost_ray lightgbm_ray petastorm ``` also re-installs the dependencies of these packages, and the `--force-reinstall` means we overwrite existing ones. This leads us to re-install the latest ray release, overwriting the wheels to be tested: ``` [INFO] 5/31/2022, 12:12:16 AM: Successfully installed ... ray-1.12.1 ... [INFO] 5/31/2022, 12:12:17 AM: * Executed RUN pip3 install -U --force-reinstall xgboost xgboost_ray petastorm (ff6ae9f9) ``` Instead, we should use `--no-deps` to avoid re-installing dependencies. Also, the wheels sanity check is moved to after installing additional packages in order to catch these errors earlier. |
||
|---|---|---|
| .. | ||
| 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