mirror of
https://github.com/vale981/ray
synced 2025-03-06 10:31:39 -05:00
b1308b1c8c
This fixes the previous problems from team column revert. This has 2 additional changes; alert handler receives the team argument, which was the root cause of breakage; https://github.com/ray-project/ray/pull/21289 Previously, tests without a team column were raising an exception, but I made the condition weaker (warning logs). I will eventually change it to raise an exception, but for smoother transition, we will log warning instead for a short time |
||
|---|---|---|
| .. | ||
| workloads | ||
| app_config.yaml | ||
| app_config_gpu.yaml | ||
| create_test_data.py | ||
| README.rst | ||
| tpl_cpu_moderate.yaml | ||
| tpl_cpu_small.yaml | ||
| tpl_gpu_small.yaml | ||
| wait_cluster.py | ||
| xgboost_tests.yaml | ||
XGBoost on Ray tests ==================== This directory contains various XGBoost on Ray release tests. You should run these tests with the `releaser <https://github.com/ray-project/releaser>`_ tool. Overview -------- There are four kinds of tests: 1. ``distributed_api_test`` - checks general API functionality and should finish very quickly (< 1 minute) 2. ``train_*`` - checks single trial training on different setups. 3. ``tune_*`` - checks multi trial training via Ray Tune. 4. ``ft_*`` - checks fault tolerance. Generally the releaser tool will run all tests in parallel, but if you do it sequentially, be sure to do it in the order above. If ``train_*`` fails, ``tune_*`` will fail, too. Acceptance criteria ------------------- These tests are considered passing when they throw no error at the end of the output log.