mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
b5b11b2d06
Please review **e2e.py and test_suite belonging to your team**! This is the first part of https://docs.google.com/document/d/16IrwerYi2oJugnRf5hvzukgpJ6FAVEpB6stH_CiNMjY/edit# This PR adds a team name to each test suite. If the name is not specified, it will be reported as unspecified. If you are running a local test, and if the new test suite doesn't have a team name specified, it will raise an exception (in this way, we can avoid missing team names in the future). Note that we will aggregate all of test config into a single file, nightly_test.yaml. |
||
|---|---|---|
| .. | ||
| workloads | ||
| app_config.yaml | ||
| cluster_cpu_moderate.yaml | ||
| cluster_cpu_small.yaml | ||
| create_test_data.py | ||
| lightgbm_tests.yaml | ||
| README.rst | ||
| requirements.txt | ||
| setup_lightgbm.sh | ||
| tpl_cpu_moderate.yaml | ||
| tpl_cpu_small.yaml | ||
| wait_cluster.py | ||
LightGBM on Ray tests ==================== This directory contains various LightGBM 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.