ray/release/lightgbm_tests
Kai Fricke 1ed8bd0345
[release/xgboost/lightgbm] Fix app config dependency install overwriting ray (#25307)
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.
2022-05-31 13:46:17 +02:00
..
workloads [ci/release] Migrate LightGBM tests (#22952) 2022-03-10 08:14:31 +00:00
app_config.yaml [release/xgboost/lightgbm] Fix app config dependency install overwriting ray (#25307) 2022-05-31 13:46:17 +02:00
app_config_gpu.yaml [release/xgboost/lightgbm] Fix app config dependency install overwriting ray (#25307) 2022-05-31 13:46:17 +02:00
create_test_data.py [CI] Format Python code with Black (#21975) 2022-01-29 18:41:57 -08:00
README.rst [release] LightGBM release tests (#17043) 2021-07-14 08:38:55 +01:00
requirements.txt [CI/docs] Remove [default] from xgboost-ray (#19186) 2021-10-14 16:29:55 +01:00
setup_lightgbm.sh [release] LightGBM release tests (#17043) 2021-07-14 08:38:55 +01:00
tpl_cpu_moderate.yaml [release] LightGBM release tests (#17043) 2021-07-14 08:38:55 +01:00
tpl_cpu_small.yaml [release] LightGBM release tests (#17043) 2021-07-14 08:38:55 +01:00
tpl_gpu_small.yaml [ci/release] Migrate LightGBM tests (#22952) 2022-03-10 08:14:31 +00:00

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.