ray/release/nightly_tests/placement_group_tests/app_config.yaml

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

python:
  pip_packages: []
  conda_packages: []

post_build_cmds:
  - pip uninstall -y ray
  - pip3 install -U {{ env["RAY_WHEELS"] | default("ray") }}
  - pip3 install -U ray[default]
  - {{ 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") }}`
Disable cpu-only-nodes preferred scheduling that breaks placement groups. (#19129) * Add a regression test for the short term * done * address code review * lint 2021-10-07 21:34:04 +09:00			`debian_packages: []`

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

			`post_build_cmds:`
			`- pip uninstall -y ray`
			`- pip3 install -U {{ env["RAY_WHEELS"] \| default("ray") }}`
			`- pip3 install -U ray[default]`
			`- {{ env["RAY_WHEELS_SANITY_CHECK"] \| default("echo No Ray wheels sanity check") }}`