ray/release/long_running_tests/app_config.yaml

base_image: {{ env["RAY_IMAGE_NIGHTLY_CPU"] | default("anyscale/ray:nightly-py37") }}
env_vars: {}

debian_packages:
  - curl
  - unzip

python:
  pip_packages:
    - "gym[atari]>=0.21.0,<0.24.1"
    - pytest
    - tensorflow
  conda_packages: []

post_build_cmds:
  - 'rm -r wrk || true && git clone https://github.com/wg/wrk.git /tmp/wrk && cd /tmp/wrk && make -j && sudo cp wrk /usr/local/bin'
  - pip3 install pytest || true
  - pip3 install -U ray[all] "gym[atari]>=0.21.0,<0.24.1" autorom[accept-rom-license]
  - pip3 install ray[all]
  # TODO (Alex): Ideally we would install all the dependencies from the new
  # version too, but pip won't be able to find the new version of ray-cpp.
  - pip3 uninstall ray -y && pip3 install -U {{ env["RAY_WHEELS"] | default("ray") }}
  - {{ env["RAY_WHEELS_SANITY_CHECK"] | default("echo No Ray wheels sanity check") }}
[ci/release] Support running tests with different python versions (#24843) 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. 2022-05-17 17:03:12 +01:00			`base_image: {{ env["RAY_IMAGE_NIGHTLY_CPU"] \| default("anyscale/ray:nightly-py37") }}`
[release tests] Fix microbenchmark base image, network overhead cluster wait time, add long running tests (#16355) 2021-06-16 21:37:17 +01:00			`env_vars: {}`
[hotfix] Fix stress_test_many_tasks cluster environment (#20519) This should fix the long running release tests that are failing to build their app configs. It seems like pip install ray[all] now downgrades the ray version. It's unclear why, but most likely, a dependency has pinned the ray version now. This PR explicitely install the version of Ray that we want after the pip install ray[all] to fix the problem. 2021-11-18 11:51:46 -08:00
[release tests] Fix microbenchmark base image, network overhead cluster wait time, add long running tests (#16355) 2021-06-16 21:37:17 +01:00			`debian_packages:`
			`- curl`
[Serve] Add serve test config files and wrk dependency (#16631) 2021-06-28 10:01:55 -07:00			`- unzip`
[release tests] Fix microbenchmark base image, network overhead cluster wait time, add long running tests (#16355) 2021-06-16 21:37:17 +01:00
			`python:`
			`pip_packages:`
Bump gym dep to 0.24 (#26190) Co-authored-by: Steven Morad <smorad@anyscale.com> Co-authored-by: Avnish <avnishnarayan@gmail.com> Co-authored-by: Avnish Narayan <38871737+avnishn@users.noreply.github.com> 2022-07-22 20:37:16 +01:00			`- "gym[atari]>=0.21.0,<0.24.1"`
[Release] Use nightly Docker images (#20001) * use nightly * switch ml cpu to ray cpu * fix * add pytest * add more pytest * add constraint * add tensorflow * fix merge conflict * add tblib * fix * add back uninstall 2021-11-10 18:00:16 -08:00			`- pytest`
			`- tensorflow`
[release tests] Fix microbenchmark base image, network overhead cluster wait time, add long running tests (#16355) 2021-06-16 21:37:17 +01:00			`conda_packages: []`

			`post_build_cmds:`
[Release] change default expiration to 2 days in order to prevent custodian kill it early morning (#17215) Co-authored-by: Jiao Dong <jiaodong@anyscale.com> 2021-07-20 17:03:14 -07:00			`- 'rm -r wrk \|\| true && git clone https://github.com/wg/wrk.git /tmp/wrk && cd /tmp/wrk && make -j && sudo cp wrk /usr/local/bin'`
[nightly] Fix pytest missing in nightly test (#20076) ## Why are these changes needed? In the nightly test we see ``` Command returned non-success status: 1; Command logs:Traceback (most recent call last): File "dask_on_ray/large_scale_test.py", line 17, in from ray._private.test_utils import monitor_memory_usage File "/home/ray/anaconda3/lib/python3.7/site-packages/ray/_private/test_utils.py", line 18, in import pytest ModuleNotFoundError: No module named 'pytest' ``` This PR fixes this error. ## Related issue number 2021-11-04 13:38:05 -07:00			`- pip3 install pytest \|\| true`
Bump gym dep to 0.24 (#26190) Co-authored-by: Steven Morad <smorad@anyscale.com> Co-authored-by: Avnish <avnishnarayan@gmail.com> Co-authored-by: Avnish Narayan <38871737+avnishn@users.noreply.github.com> 2022-07-22 20:37:16 +01:00			`- pip3 install -U ray[all] "gym[atari]>=0.21.0,<0.24.1" autorom[accept-rom-license]`
[Release] Use nightly Docker images (#20001) * use nightly * switch ml cpu to ray cpu * fix * add pytest * add more pytest * add constraint * add tensorflow * fix merge conflict * add tblib * fix * add back uninstall 2021-11-10 18:00:16 -08:00			`- pip3 install ray[all]`
[hotfix] Fix stress_test_many_tasks cluster environment (#20519) This should fix the long running release tests that are failing to build their app configs. It seems like pip install ray[all] now downgrades the ray version. It's unclear why, but most likely, a dependency has pinned the ray version now. This PR explicitely install the version of Ray that we want after the pip install ray[all] to fix the problem. 2021-11-18 11:51:46 -08:00			`# TODO (Alex): Ideally we would install all the dependencies from the new`
			`# version too, but pip won't be able to find the new version of ray-cpp.`
[CI] [Release] uninstall Ray before installing new Ray version (#21159) 2021-12-17 16:25:15 -08:00			`- pip3 uninstall ray -y && pip3 install -U {{ env["RAY_WHEELS"] \| default("ray") }}`
[ci/release] Add sanity check for ray wheels hash to release tests (#18489) 2021-09-10 17:50:31 +01:00			`- {{ env["RAY_WHEELS_SANITY_CHECK"] \| default("echo No Ray wheels sanity check") }}`