Jiajun Yao
b69b9299e6
[Core] Fix check failure RAY_CHECK(it != current_tasks_.end()); (#47659)
|
1 周之前 | |
|---|---|---|
| .. | ||
| bisect | 5 月之前 | |
| hooks | 6 月之前 | |
| macos | 4 月之前 | |
| release | 2 月之前 | |
| release-automation | 2 月之前 | |
| .sunset_civ1_linux | 10 月之前 | |
| README.md | 2 年之前 | |
| _forge.rayci.yml | 2 月之前 | |
| base.rayci.yml | 2 月之前 | |
| build.rayci.yml | 2 月之前 | |
| cicd.rayci.yml | 5 月之前 | |
| copy_files.py | 1 年之前 | |
| core.rayci.yml | 1 周之前 | |
| data.rayci.yml | 2 月之前 | |
| kuberay.rayci.yml | 4 月之前 | |
| lint.rayci.yml | 1 月之前 | |
| linux_aarch64.rayci.yml | 1 月之前 | |
| macos.rayci.yml | 7 月之前 | |
| ml.rayci.yml | 2 月之前 | |
| others.rayci.yml | 2 月之前 | |
| releasebuild.rayci.yml | 8 月之前 | |
| rllib.rayci.yml | 1 月之前 | |
| rllib_contrib.rayci.yml | 7 月之前 | |
| serve.rayci.yml | 3 月之前 | |
| serverless.rayci.yml | 7 月之前 | |
| windows.rayci.yml | 3 月之前 | |
README.md
Buildkite pipelines
This directory contains buildkite pipelines used to start CI tests.
Each step contains a buildkite step that is parsed and executed according to the Buildkite pipeline specification.
Conditions
An extra optional field conditions is defined, which includes conditions under which tests are run.
The script ci/pipeline/determine_tests_to_run.py determines changed files in a PR and only kicks off
tests that include at least one of the conditions. If no condition is specified, the test is always run.
A special case is the NO_WHEELS_REQUIRED condition. If this is present, it indicates that the test can
be run with the latest available binaries - in this case the test can be started early, as it will re-use
the latest branch image and only check out the current code revision in the PR. This early kick off will
only trigger on PR builds, not on branch builds.
Pipelines
This directory should be considered with respect to the docker images located in ci/docker.
pipeline.build.ymlcontains jobs that require build dependencies. This includes all tests that re-build Ray (e.g. when switching Python versions). The tests are run on thebuild.Dockerfileimage.pipeline.test.ymlcontains jobs that only require an installed Ray and a small subset of dependencies, notably exlcuding ML libraries such as Tensorflow or Torch. The tests are run on thetest.Dockerfileimage.pipeline.ml.ymlcontains jobs that require ML libraries Tensorflow and Torch to be available. The tests are run on theml.Dockerfileimage.pipeline.gpu.ymlcontains jobs that require one GPU. The tests are run on thegpu.Dockerfileimage.pipeline.gpu.large.ymlcontains jobs that require multi-GPUs (currently 4). The tests are run on thegpu.Dockerfileimage.