hiro/ray
1
0
Fork 0
mirror of https://github.com/vale981/ray synced 2025-03-06 02:21:39 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
ray/release/ray_release/schema.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

219 lines
3.5 KiB
JSON
Raw Normal View History

[ci/release] Add schema validation for release test config (#22919) To avoid breakage like in #22905, this PR adds schema validation to the release test package. In a follow-up PR, we'll likely switch this to use pydantic instead.
2022-03-09 09:50:51 +00:00
{
"$schema": "http://json-schema.org/draft-06/schema#",
"$ref": "#/definitions/Test",
"definitions": {
"Test": {
"type": "object",
"additionalProperties": false,
"properties": {
"name": {
"type": "string"
},
"group": {
"type": "string"
},
"working_dir": {
"type": "string"
},
[ci/release] Support running tests on staging (#25889) This adds "environments" to the release package that can be used to configure some environment variables. These variables will be loaded either by an `--env` argument or a `env` definition in the test definition and can be used to e.g. run release tests on staging.
2022-06-28 18:14:01 +01:00
"env": {
"type": "string"
},
[ci/release] Add schema validation for release test config (#22919) To avoid breakage like in #22905, this PR adds schema validation to the release test package. In a follow-up PR, we'll likely switch this to use pydantic instead.
2022-03-09 09:50:51 +00:00
"legacy": {
"$ref": "#/definitions/Legacy"
},
[ci/release] Validate smoke test fields, enforce frequency (#23075) Of all smoke test arguments, frequency is the only required one, so we should check for it. Additionally, not all fields should be able to be overwritten (e.g. legacy or name), so we enforce this as well.
2022-03-13 18:48:03 +00:00
"stable": {
"type": "boolean"
},
[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
"python": {
"type": "string",
"enum": [
"3.6",
"3.7",
"3.8",
"3.9"
]
},
[ci/release] Add schema validation for release test config (#22919) To avoid breakage like in #22905, this PR adds schema validation to the release test package. In a follow-up PR, we'll likely switch this to use pydantic instead.
2022-03-09 09:50:51 +00:00
"frequency": {
"type": "string",
"enum": [
"disabled",
"multi",
"nightly",
"weekly"
]
},
"team": {
"type": "string"
},
"driver_setup": {
"type": "string"
},
"cluster": {
"$ref": "#/definitions/Cluster"
},
"run": {
"$ref": "#/definitions/Run"
},
"smoke_test": {
"$ref": "#/definitions/SmokeTest"
},
"alert": {
"type": "string"
}
},
"required": [
"cluster",
"frequency",
"name",
"run",
"team",
"working_dir"
],
"title": "Test"
},
"Cluster": {
"type": "object",
"additionalProperties": false,
"properties": {
"cluster_env": {
"type": "string"
},
"cluster_compute": {
"type": "string"
},
"autosuspend_mins": {
"type": "integer",
"minimum": -1
},
"cloud_id": {
"type": "string"
},
"cloud_name": {
"type": "string"
}
},
"required": [
"cluster_compute",
"cluster_env"
],
"title": "Cluster"
},
"Legacy": {
"type": "object",
"additionalProperties": false,
"properties": {
"test_name": {
"type": "string"
},
"test_suite": {
"type": "string"
}
},
"required": [
"test_name",
"test_suite"
],
"title": "Legacy"
},
"Run": {
"type": "object",
"additionalProperties": false,
"properties": {
"type": {
"type": "string",
"enum": [
"command",
"sdk_command",
"job",
"client"
]
},
"file_manager": {
"type": "string",
"enum": [
"sdk",
"client",
"job"
]
},
"wait_for_nodes": {
"$ref": "#/definitions/WaitForNodes"
},
"prepare": {
"type": "string"
},
"prepare_timeout": {
"type": "integer"
},
"script": {
"type": "string"
},
"timeout": {
"type": "integer"
},
[ci/release] Validate smoke test fields, enforce frequency (#23075) Of all smoke test arguments, frequency is the only required one, so we should check for it. Additionally, not all fields should be able to be overwritten (e.g. legacy or name), so we enforce this as well.
2022-03-13 18:48:03 +00:00
"long_running": {
"type": "boolean"
}
[ci/release] Add schema validation for release test config (#22919) To avoid breakage like in #22905, this PR adds schema validation to the release test package. In a follow-up PR, we'll likely switch this to use pydantic instead.
2022-03-09 09:50:51 +00:00
},
"required": [
"script",
"timeout"
],
"title": "Run"
},
"WaitForNodes": {
"type": "object",
"additionalProperties": false,
"properties": {
"num_nodes": {
"type": "integer"
},
"timeout": {
"type": "integer"
}
},
"required": [
[Nightly tests] Increase wait for nodes timeout (#24457) Although there's enough quota, it is possible the AWS doesn't have enough capacity to start up new nodes. According to @allenyin55, the current wait for node timeout is too short. This PR increases the timeout to 3000 seconds (50 minutes) from 600 seconds. Let's see if this can resolve the issue. If it makes things worse, I will revert it quickly (I will closely monitor the infra failure rate)
2022-05-05 11:42:21 +09:00
"num_nodes"
[ci/release] Add schema validation for release test config (#22919) To avoid breakage like in #22905, this PR adds schema validation to the release test package. In a follow-up PR, we'll likely switch this to use pydantic instead.
2022-03-09 09:50:51 +00:00
],
"title": "WaitForNodes"
},
"SmokeTest": {
"type": "object",
[ci/release] Validate smoke test fields, enforce frequency (#23075) Of all smoke test arguments, frequency is the only required one, so we should check for it. Additionally, not all fields should be able to be overwritten (e.g. legacy or name), so we enforce this as well.
2022-03-13 18:48:03 +00:00
"additionalProperties": false,
"title": "SmokeTest",
"properties": {
"working_dir": {
"type": "string"
},
[ci/release] Support running tests on staging (#25889) This adds "environments" to the release package that can be used to configure some environment variables. These variables will be loaded either by an `--env` argument or a `env` definition in the test definition and can be used to e.g. run release tests on staging.
2022-06-28 18:14:01 +01:00
"env": {
"type": "string"
},
[ci/release] Validate smoke test fields, enforce frequency (#23075) Of all smoke test arguments, frequency is the only required one, so we should check for it. Additionally, not all fields should be able to be overwritten (e.g. legacy or name), so we enforce this as well.
2022-03-13 18:48:03 +00:00
"driver_setup": {
"type": "string"
},
"cluster": {
"type": "object"
},
"run": {
"type": "object"
},
"alert": {
"type": "string"
},
"frequency": {
"type": "string",
"enum": [
"disabled",
"multi",
"nightly",
"weekly"
]
}
},
"required": [
"frequency"
]
[ci/release] Add schema validation for release test config (#22919) To avoid breakage like in #22905, this PR adds schema validation to the release test package. In a follow-up PR, we'll likely switch this to use pydantic instead.
2022-03-09 09:50:51 +00:00
}
}
[ci/release] Validate smoke test fields, enforce frequency (#23075) Of all smoke test arguments, frequency is the only required one, so we should check for it. Additionally, not all fields should be able to be overwritten (e.g. legacy or name), so we enforce this as well.
2022-03-13 18:48:03 +00:00
}
Reference in a new issue Copy permalink