mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
![]() OSS release tests currently run with hardcoded Python 3.7 base. In the future we will want to run tests on different python versions. This PR adds support for a new `python` field in the test configuration. The python field will determine both the base image used in the Buildkite runner docker container (for Ray client compatibility) and the base image for the Anyscale cluster environments. Note that in Buildkite, we will still only wait for the python 3.7 base image before kicking off tests. That is acceptable, as we can assume that most wheels finish in a similar time, so even if we wait for the 3.7 image and kick off a 3.8 test, that runner will wait maybe for 5-10 more minutes. |
||
---|---|---|
.. | ||
learning_tests | ||
multi_gpu_learning_tests | ||
multi_gpu_with_attention_learning_tests | ||
multi_gpu_with_lstm_learning_tests | ||
stress_tests | ||
unit_gpu_tests | ||
1gpu_4cpus.yaml | ||
2gpus_32cpus.yaml | ||
4gpus_64cpus.yaml | ||
4gpus_544_cpus.yaml | ||
8gpus_64cpus.yaml | ||
8gpus_96cpus.yaml | ||
12gpus_192cpus.yaml | ||
app_config.yaml | ||
README.rst |
RLlib Tests =========== This directory contains various RLlib release tests. You should run these tests with the `releaser <https://github.com/ray-project/releaser>`_ tool. Overview -------- Currently, there are 3 RLlib tests: 1. ``learning_tests`` - Tests, whether major algos (tf+torch) can learn in Atari or PyBullet envs in ~30-60min. 1. ``stress_tests`` - Runs 4 IMPALA Atari jobs, each one using 1GPU and 128CPUs (needs autoscaling to succeed). 1. ``unit_gpu_tests`` - Tests, whether all of RLlib's example scripts can be run on a GPU. Generally the releaser tool will run all tests in parallel. Acceptance criteria ------------------- These tests are considered passing when they throw no error at the end of the output log.