# PyTorch adds XPU CI gating for Kineto plugin changes

> **Key takeaway:** PyTorch now triggers XPU continuous integration tests when changes are made to the Kineto plugin to prevent build breakages.

**Published:** 2026-10-16T12:15:23+00:00 
**Source:** PyTorch GitHub Releases 
**Category:** bigtech-foss 
**Canonical URL:** https://fosswire.org/news/pytorch-adds-xpu-ci-gating-for-kineto-plugin-changes.html 

## Summary
A new update to the PyTorch repository introduces a safety mechanism to run XPU continuous integration (CI) tests when the third_party/kineto directory is modified. Previously, changes to the Kineto XPU plugin could bypass XPU-specific testing, leading to broken builds on Linux and Windows. This change implements a gating mechanism similar to those used for third_party/fbgemm.

## Preventing XPU build failures
- Implements a gating mechanism for the **third_party/kineto** path.
- Ensures that changes to the Kineto XPU plugin trigger the **ciflow/xpu** label.
- Prevents regressions in build jobs such as **linux-jammy-xpu-n-1-py3.10** and **win-vs2022-xpu-n-1-py3**.
- Aligns Kineto's CI logic with existing rules used for **third_party/fbgemm** (e.g., b200, h100, and rocm-mi300 rules).

## Why it matters
This improves the stability of PyTorch builds for users relying on XPU hardware by ensuring third-party plugin updates are properly validated.