eval/schema/machine.schema.json

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://github.com/amd/skills/eval/schema/machine.schema.json",
  "title": "AMD skill eval machine requirements",
  "description": "Optional file at skills/<name>/evals/machine.yml, present ONLY for a skill whose behavior cases cannot run on the default runners on every platform. Absent means the default Strix Halo runners on Linux and Windows, which is the common case. Say which class of machine you need and which platforms to use; everything that follows from the class -- the runs-on labels, the pull-request label rationing it, the environment holding its credentials -- is resolved by eval/datasets.py, not restated here.",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "runner_type": {
      "type": "string",
      "enum": ["default", "instinct"],
      "default": "default",
      "description": "The class of machine the behavior cases need. `default` is the shared Strix Halo pool and is assumed when this key is absent. `instinct` is the AMD Instinct GPU runner: Linux only, always gated on the enable_mi_ci pull-request label, and always run with its own scoped credentials."
    },
    "os": {
      "type": "array",
      "minItems": 1,
      "items": { "type": "string", "enum": ["Linux", "Windows"] },
      "description": "Which platforms to exercise, defaulting to every platform the runner_type exists on. Narrow it for a skill that shells out to platform-specific tooling, which replaces the pytest.mark.skipif guards this format retired. Must be a subset of what the runner_type supports, so [\"Windows\"] with runner_type instinct is an error rather than a job that never schedules."
    }
  }
}