mirror of
https://github.com/pytorch/pytorch.git
synced 2025-10-20 12:54:11 +08:00
`inductor` and `rocm` workflows are the major contributors to the CI load on ROCm CI at the moment, resulting in huge backlogs: https://github.com/pytorch/pytorch/pull/131489#issue-2425804464 * Move rocm.yml to cron frequency * Move ROCm CI jobs from inductor.yml to inductor-rocm.yml * Introduce `ciflow/inductor-rocm` as PR label to manually invoke inductor jobs for ROCm (no automatic invoking to limit CI load) * After this PR, only `trunk` workflow jobs for ROCm will run on every commit and PR merge, but since they take 45min*3 time on average, I decided to leave them as-is since it will provide us some basic insulation against ROCm breakage. Pull Request resolved: https://github.com/pytorch/pytorch/pull/131637 Approved by: https://github.com/clee2000, https://github.com/atalman, https://github.com/huydhn
31 lines
610 B
YAML
31 lines
610 B
YAML
tracking_issue: 24422
|
|
ciflow_tracking_issue: 64124
|
|
ciflow_push_tags:
|
|
- ciflow/binaries
|
|
- ciflow/binaries_conda
|
|
- ciflow/binaries_libtorch
|
|
- ciflow/binaries_wheel
|
|
- ciflow/inductor
|
|
- ciflow/inductor-rocm
|
|
- ciflow/inductor-perf-compare
|
|
- ciflow/inductor-micro-benchmark
|
|
- ciflow/inductor-cu124
|
|
- ciflow/linux-aarch64
|
|
- ciflow/mps
|
|
- ciflow/nightly
|
|
- ciflow/periodic
|
|
- ciflow/rocm
|
|
- ciflow/slow
|
|
- ciflow/trunk
|
|
- ciflow/unstable
|
|
- ciflow/xpu
|
|
- ciflow/torchbench
|
|
retryable_workflows:
|
|
- pull
|
|
- trunk
|
|
- linux-binary
|
|
- windows-binary
|
|
labeler_config: labeler.yml
|
|
label_to_label_config: label_to_label.yml
|
|
mergebot: True
|