ray/release/nightly_tests/many_nodes_tests/app_config.yaml

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

python:
  pip_packages: []
  conda_packages: []

post_build_cmds:
  - pip3 uninstall -y ray && pip3 install -U {{ env["RAY_WHEELS"] | default("ray") }}
  - pip3 install -U ray[default]
  - echo {{env["DATESTAMP"]}}
  - {{ 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") }}`
Fix wrong many_nodes_actor_test app config (#21404) RAY_GCS_ACTOR_SCHEDULING_ENABLED is wrong should be RAY_gcs_actor_scheduling_enabled. Since gcs based actor scheduling is not enabled yet so I just removed this flag. 2022-01-05 11:52:13 -08:00			`env_vars: {"RAY_gcs_server_rpc_server_thread_num": "8"}`
[test] Add x nodes y actors test to nightly tests (#18291) 2021-09-03 18:54:23 -07:00			`debian_packages: []`

			`python:`
			`pip_packages: []`
			`conda_packages: []`

			`post_build_cmds:`
[Nightly test] Move two line downloads to one line. (#25061) It fixes the mysterious error when all cluster env build is failing when pip uninstall / pip install is written in 2 lines. The root cause will be fixed later 2022-05-22 16:07:03 +09:00			`- pip3 uninstall -y ray && pip3 install -U {{ env["RAY_WHEELS"] \| default("ray") }}`
[test] Add x nodes y actors test to nightly tests (#18291) 2021-09-03 18:54:23 -07:00			`- pip3 install -U ray[default]`
			`- echo {{env["DATESTAMP"]}}`
[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") }}`