Ship a prebuilt C++ SDK in the ExecuTorch Linux wheel by shoumikhin · Pull Request #21470 · pytorch/executorch

shoumikhin · 2026-07-29T19:49:19Z

Why this is needed

Today, using the ExecuTorch runtime from a C++ program means building
ExecuTorch from source: clone the repo, sync submodules, and run a CMake
build before you can compile and link your own runner. The pip wheel only
ships the Python runtime module (_portable_lib) plus a small set of
headers meant for authoring custom operators. There is no way to just
pip install executorch and link a standalone C++ application against the
runtime.

This is friction for anyone whose deployment path is C++ (the common case
for on-device inference) and who already has the wheel installed for
export. The runtime is compiled during the wheel build and then discarded.

This change ships the runtime as a linkable shared library, its public
headers, and a CMake package config inside the Linux wheel, so a C++
program can link the ExecuTorch runtime with no source checkout and no
separate build.

What is inside

Added to the Linux wheel (nothing removed; other platforms unchanged):

executorch/lib/libexecutorch.so (SONAME-versioned, with the standard
libexecutorch.so -> .so.1 -> .so.<version> chain): the consolidated
shared runtime. It bundles the runtime core plus the common runtime
extensions (module, tensor, data_loader, flat_tensor, named_data_map).
executorch/include/executorch/extension/...: the public headers for the
Module, Tensor, DataLoader, FlatTensor (.ptd reader), NamedDataMap, and
header-only MallocMemoryAllocator APIs. Runtime/Program/backend headers
were already shipped and are reused.
executorch/share/cmake/executorch-config.cmake: a CMake package config
that exposes an executorch::runtime imported target (plus convenience
aliases executorch::core, executorch::extension_*).
executorch/utils/cmake_prefix_path: a small helper (mirrors
torch.utils.cmake_prefix_path) so CMake can find the config in one line.

Why a shared library (not static archives)

The runtime is shipped shared on purpose. ExecuTorch keeps a single
process-global backend/kernel registry. Shipping the runtime as one shared
libexecutorch.so lets a separately distributed backend or delegate shared
library register into that one registry: the backend .so is built without
its own copy of the runtime (its register_backend reference is undefined
and resolves against libexecutorch.so at load), and its static-init
registration runs when the .so is loaded (via whole-archive for a C++ app,
or an explicit import/dlopen for Python, which is how ExecuTorch already
ships the QNN backend today). Static archives would give each consumer its
own private registry, which cannot support loading multiple independently
distributed backends into one runtime.

The set is intentionally libtorch-free and excludes the general CPU
operator/kernel libraries, because a delegate supplies its own compute. It
is also Linux only: the .so naming and SONAME symlink chain are Unix
specific, so the Windows and macOS wheels are byte-identical to before.

How to use it

pip install executorch

find_package(executorch CONFIG REQUIRED)

add_executable(my_runner main.cpp)
target_link_libraries(my_runner PRIVATE executorch::runtime)

cmake -S . -B build \
  -DCMAKE_PREFIX_PATH="$(python -c 'import executorch.utils as u; print(u.cmake_prefix_path)')"
cmake --build build

Existing consumers that use find_package(executorch) to link the Python
_portable_lib for custom-op extensions keep working unchanged. The new
C++ SDK availability is reported separately via EXECUTORCH_SDK_FOUND, so
the legacy EXECUTORCH_FOUND / EXECUTORCH_LIBRARIES contract is
preserved.

Test plan

Verified on Linux x86_64:

Built the wheel with python setup.py bdist_wheel and confirmed it
contains libexecutorch.so with its SONAME symlink chain, the CMake
config, the utils helper, and the new extension headers, and that
headers with no shipped implementation are excluded.
Installed the wheel into a clean virtual environment and built a small
standalone C++ runner against it with find_package(executorch) and
executorch.utils.cmake_prefix_path. The runner compiled, linked, ran,
and initialized the runtime.
Built a separate "coreless" backend shared library (no bundled runtime,
register_backend left undefined) and confirmed that loading it against
the installed libexecutorch.so registers the backend into the runtime's
registry (get_backend_class goes from not-found to found). This is the
mechanism that lets independently distributed backends coalesce into one
runtime.
Confirmed the runner and the runtime link no libtorch/libc10 (via ldd).
Confirmed the Windows and macOS wheel code paths add nothing new, so those
wheels are unaffected.
Lint and format pass (flake8, ufmt, cmake-format).

Known limitation: the wheel-build step stores the SONAME symlinks as plain
file copies rather than symlinks. Linking and loading still work because the
SONAME target is present as a real file; a follow-up can preserve them as
true symlinks to save space.

CI

Adds a PR job (test-cpp-sdk-wheel-linux in pull.yml, calling
.ci/scripts/test_cpp_sdk_wheel.sh) that builds the wheel, installs it into a
clean venv, and uses find_package(executorch) to build a C++ consumer linking
executorch::runtime, then loads a coreless backend shared library and asserts
it registers into libexecutorch.so. This gives the feature direct coverage:
before, no PR job built the full wheel or linked the C++ SDK.

pytorch-bot · 2026-07-29T19:49:23Z

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21470

📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 33 New Failures, 160 Pending, 11 Unclassified Failures

As of commit 1bc3075 with merge base 0b13b6a ():

NEW FAILURES - The following jobs have failed:

Lint / link-check / lint-urls (gh)
Lint / lintrunner-mypy (gh)
>>> Lint for backends/cortex_m/quantizer/pattern_matcher.py:
pull / test-arm-backend-no-driver (test_pytest_models_tosa) / linux-job (gh)
RuntimeError: Command docker exec -t de39a181ec007013250c666f8fcba87eeda5f21cf9abd213f30768c0a6af578a /exec failed with exit code 1
pull / test-arm-backend-no-driver (test_pytest_ops_no_target) / linux-job (gh)
RuntimeError: Command docker exec -t 7af2f8d775ceb11cb90f137b8af8554e4eba8606615767cd40e8045e160762ba /exec failed with exit code 1
pull / test-arm-backend-no-driver (test_pytest_ops_tosa) / linux-job (gh)
RuntimeError: Command docker exec -t 9c38c9a0ff812bf5a81ac4062dfec0675def2fc1bfb0e239cf62dbb1bbd62b79 /exec failed with exit code 1
pull / test-arm-backend-no-driver (test_run_tosa) / linux-job (gh)
RuntimeError: Command docker exec -t 2a0104e38ea1e4f5301dd6ac8053fab481e914c4b5d53a9acb776d141dcbc4f3 /exec failed with exit code 1
pull / test-arm-cortex-m-size-test (bare_metal) / linux-job (gh)
RuntimeError: Command docker exec -t 419a7ec568f02c6703d03c1150a990af1cbcc26e0fe2d61ddc71489253a84fc0 /exec failed with exit code 1
pull / test-arm-cortex-m-size-test (zephyr-preset) / linux-job (gh)
RuntimeError: Command docker exec -t 34ed17e35064770efca6d7eeca6c28147e9974590eed456b54842ed95445b9c2 /exec failed with exit code 1
pull / test-mcu-cortex-m-backend / linux-job (gh)
RuntimeError: Command docker exec -t b46c408d7e1301494138b4f518c53d373e856f85270aa6700670e9ca5e7a8da9 /exec failed with exit code 1
pull / test-qnn-delegate-linux / linux-job (gh)
RuntimeError: Command docker exec -t 403d9876d9ffc97a86d6ba3d863bac27c53ab7785eeb297c1f2f65a6ddeea45f /exec failed with exit code 92
pull / unittest / linux / linux-job (gh)
RuntimeError: Command docker exec -t f9ad84f1aa6f49bfa3317cd2aab8112e0dc9e46345108e60ae46c77175b13df8 /exec failed with exit code 1
pull / unittest-editable / linux / linux-job (gh)
RuntimeError: Command docker exec -t f74fe29655dca2fc53c50ada3c36ef5ad4dbb4ac5cc4e09fd54a3addebccdec6 /exec failed with exit code 1
Test ARM Backend / test-arm / test-backend-linux (arm_tosa_fp, models) / linux-job (gh)
RuntimeError: Command docker exec -t c4b6dc2e1259d00b281a752b242301599b533607d33b54dd71f8a8b9c0356a21 /exec failed with exit code 1
Test ARM Backend / test-arm / test-backend-linux (arm_tosa_fp, operators) / linux-job (gh)
RuntimeError: Command docker exec -t 34e9fac8b54cd52038ab19fa742530e397ad158ec1d2d4c2bb676f325ec27518 /exec failed with exit code 1
Test ARM Backend / test-arm / test-backend-linux (arm_vgf_fp, models) / linux-job (gh)
RuntimeError: Command docker exec -t 9040948b129db49af7e3b689a34bcb5903985edba6092effe3f3169e748ac2fa /exec failed with exit code 1
Test ARM Backend / test-arm / test-backend-linux (arm_vgf_fp, operators) / linux-job (gh)
RuntimeError: Command docker exec -t 0c2a00f727d4453da0be763205b04839de93e34cdbdd32d2257a227700afdb25 /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_deit_e2e_ethos_u) / linux-job (gh)
RuntimeError: Command docker exec -t c0930cc3c82a9e79990efa92e5c3bb3e4f220e20f69a23cf18b158ee9dc017cb /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_memory_allocation) / linux-job (gh)
RuntimeError: Command docker exec -t 0fe406933e071713f8d72b23e0ae0cfba1042216cdfa5f7cb7b9807bd150821e /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_model_smollm2_135M_ethos_u85) / linux-job (gh)
RuntimeError: Command docker exec -t d72bcfd9ec8e1c26dfb7ddd26e0495370bed137dbac7eaf59aaa613bb77aebf9 /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_ootb_tests_ethos_u) / linux-job (gh)
RuntimeError: Command docker exec -t 047ae06316e69813bf3101eade43aa4955033f8abddcf418a87d676ebaf07476 /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_ootb_tests_tosa) / linux-job (gh)
RuntimeError: Command docker exec -t 35bfd9a32755c822de4ab1f908a1ff65d00577c767ca5be617d79d6251e5d99d /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_pytest_models_ethos_u55) / linux-job (gh)
RuntimeError: Command docker exec -t ad5539baa55ed774c6a0ffe8cb19039fbca667b2b661a1356c361b6ea7783996 /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_pytest_models_ethos_u85) / linux-job (gh)
RuntimeError: Command docker exec -t 26ffd2b107eedac6f7822f8d9513ec94031b47fcdff0964e1e0bc95232fb1921 /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_pytest_ops_ethos_u55) / linux-job (gh)
RuntimeError: Command docker exec -t 838a47eaa6f095c8a6d506f99886bd50e58a1375a757058c811da019df463018 /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_pytest_ops_ethos_u85) / linux-job (gh)
RuntimeError: Command docker exec -t be41b3ef0b288213695aa0933a68d16ce8e5221119af5e155cb8ee1f77b1ac3e /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_run_ethos_u55) / linux-job (gh)
RuntimeError: Command docker exec -t 40311b2cf54b3086cae9563ed4fa47fa60056bea083e815d00e3d1756d38a9ae /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_run_ethos_u85) / linux-job (gh)
RuntimeError: Command docker exec -t 7bf58edf27061bc252170b2e7fc911b1d2bb85eb29abb0f3a685af97348328ad /exec failed with exit code 1
trunk / test-arm-backend-ethos-u (test_smaller_stories_llama_tosa) / linux-job (gh)
RuntimeError: Command docker exec -t fc8a249d03a5cb46cdfa3d094317f310f69354e22e0ca7b3d27dc53cf044a19d /exec failed with exit code 1
trunk / test-arm-backend-vkml (test_ootb_tests_vgf) / linux-job (gh)
RuntimeError: Command docker exec -t 96919a6cb35adba336f7a1ab0216690e02123ff59b13a77457f25d290f2ed74e /exec failed with exit code 1
trunk / test-arm-backend-vkml (test_pytest_models_vkml) / linux-job (gh)
RuntimeError: Command docker exec -t 06e079c7904af3c2935874b720b6fb888c36c5528237419a4d28aa91046f6ba7 /exec failed with exit code 1
trunk / test-arm-backend-vkml (test_pytest_ops_vkml) / linux-job (gh)
RuntimeError: Command docker exec -t e157fe264371e3e4425e735f43f775fc52c422f0ffecf296603d0ed6de44ddeb /exec failed with exit code 1
trunk / test-arm-backend-vkml (test_smaller_stories_llama_vkml) / linux-job (gh)
RuntimeError: Command docker exec -t 27dda60ca80d26c9c17631691fa8ead7ea9cb2dccdfd0486ff6b642e932e0a2c /exec failed with exit code 1
trunk / unittest-release / linux / linux-job (gh)
RuntimeError: Command docker exec -t 6cd0a07dcead5cf4b9f6c510dcfad37275e77dc96bd71ea1e7c36b68b55b2693 /exec failed with exit code 1

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

pull / test-arm-backend-public-api-backward-compatibility / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t e9cda3ffbdf4decf7782c4259fad8f4a38d9d28f68a3365e80cd78cf1f32ca4f /exec failed with exit code 1
pull / test-qnn-direct-build-linux / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t d1a01bea4b4f216a23b229d35d57ed8251236acb74391a45765135a7345ef26a /exec failed with exit code 127
Test QNN Windows MSVC build / build-qnn-windows-msvc / windows-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
trunk / test-cortex-m-e2e / run (mv2, cortex-m0plus) / mv2-cortex-m0plus (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t 29eebdb0a9650f2793029e18f2b79b5ea2e7da10ba7330afa3f57baa4fe3db4e /exec failed with exit code 1
trunk / test-cortex-m-e2e / run (mv2, cortex-m55) / mv2-cortex-m55 (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t 407771c62fc99c527136af63b61d01194520f86fc3d7bfca3e3ed16148ac4b4d /exec failed with exit code 1
trunk / test-cortex-m-e2e / run (mv2, cortex-m7) / mv2-cortex-m7 (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t 3450717ed9a2d359d556f07ee7488e76a675b7e2574360d59a7f0c11914dbfab /exec failed with exit code 1
trunk / test-cortex-m-e2e / run (mv3, cortex-m0plus) / mv3-cortex-m0plus (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t 1f04d0988fe81b80a987db67a582da7851da66cf9e903a2aaf0de6bab10ab7c3 /exec failed with exit code 1
trunk / test-cortex-m-e2e / run (mv3, cortex-m55) / mv3-cortex-m55 (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t ed876fc9b8e53f0060313d121228c9efa774f7cd577d272a6fd42cbcf927ca58 /exec failed with exit code 1
trunk / test-cortex-m-e2e / run (mv3, cortex-m7) / mv3-cortex-m7 (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t 326354f08e1d826d826042339a75136f00086c953ce872738880ec6e3261becb /exec failed with exit code 1
trunk / test-cortex-m-ops / run (cortex-m0plus) / cortex-m-ops-cortex-m0plus (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t 7d93c093f9c82a7172107fa8a71ff8337a74827efe838ec73b3b64b9309ba190 /exec failed with exit code 1
trunk / test-cortex-m-ops / run (cortex-m7) / cortex-m-ops-cortex-m7 (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
RuntimeError: Command docker exec -t 14b1a7b653f242a54898be5fa82381d075ac01ff95f530e29a1b7bffd46e484b /exec failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

github-actions · 2026-07-29T19:50:12Z

This PR needs a `release notes:` label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

## Why this is needed Today, using the ExecuTorch runtime from a C++ program means building ExecuTorch from source: clone the repo, sync submodules, and run a CMake build before you can compile and link your own runner. The pip wheel only ships the Python runtime module (`_portable_lib`) plus a small set of headers meant for authoring custom operators. There is no way to just `pip install executorch` and link a standalone C++ application against the runtime. This is friction for anyone whose deployment path is C++ (the common case for on-device inference) and who already has the wheel installed for export. The runtime is compiled during the wheel build and then discarded. This change ships the runtime as a linkable shared library, its public headers, and a CMake package config inside the Linux wheel, so a C++ program can link the ExecuTorch runtime with no source checkout and no separate build. ## What is inside Added to the Linux wheel (nothing removed; other platforms unchanged): - `executorch/lib/libexecutorch.so` (SONAME-versioned, with the standard `libexecutorch.so -> .so.1 -> .so.<version>` chain): the consolidated shared runtime. It bundles the runtime core plus the common runtime extensions (module, tensor, data_loader, flat_tensor, named_data_map). - `executorch/include/executorch/extension/...`: the public headers for the Module, Tensor, DataLoader, FlatTensor (.ptd reader), NamedDataMap, and header-only MallocMemoryAllocator APIs. Runtime/Program/backend headers were already shipped and are reused. - `executorch/share/cmake/executorch-config.cmake`: a CMake package config that exposes an `executorch::runtime` imported target (plus convenience aliases `executorch::core`, `executorch::extension_*`). - `executorch/utils/cmake_prefix_path`: a small helper (mirrors `torch.utils.cmake_prefix_path`) so CMake can find the config in one line. ## Why a shared library (not static archives) The runtime is shipped shared on purpose. ExecuTorch keeps a single process-global backend/kernel registry. Shipping the runtime as one shared `libexecutorch.so` lets a separately distributed backend or delegate shared library register into that one registry: the backend `.so` is built without its own copy of the runtime (its `register_backend` reference is undefined and resolves against `libexecutorch.so` at load), and its static-init registration runs when the `.so` is loaded (via whole-archive for a C++ app, or an explicit import/dlopen for Python, which is how ExecuTorch already ships the QNN backend today). Static archives would give each consumer its own private registry, which cannot support loading multiple independently distributed backends into one runtime. The set is intentionally libtorch-free and excludes the general CPU operator/kernel libraries, because a delegate supplies its own compute. It is also Linux only: the `.so` naming and SONAME symlink chain are Unix specific, so the Windows and macOS wheels are byte-identical to before. ## How to use it ```bash pip install executorch ``` ```cmake find_package(executorch CONFIG REQUIRED) add_executable(my_runner main.cpp) target_link_libraries(my_runner PRIVATE executorch::runtime) ``` ```bash cmake -S . -B build \ -DCMAKE_PREFIX_PATH="$(python -c 'import executorch.utils as u; print(u.cmake_prefix_path)')" cmake --build build ``` Existing consumers that use `find_package(executorch)` to link the Python `_portable_lib` for custom-op extensions keep working unchanged. The new C++ SDK availability is reported separately via `EXECUTORCH_SDK_FOUND`, so the legacy `EXECUTORCH_FOUND` / `EXECUTORCH_LIBRARIES` contract is preserved. ## Test plan Verified on Linux x86_64: - Built the wheel with `python setup.py bdist_wheel` and confirmed it contains `libexecutorch.so` with its SONAME symlink chain, the CMake config, the `utils` helper, and the new extension headers, and that headers with no shipped implementation are excluded. - Installed the wheel into a clean virtual environment and built a small standalone C++ runner against it with `find_package(executorch)` and `executorch.utils.cmake_prefix_path`. The runner compiled, linked, ran, and initialized the runtime. - Built a separate "coreless" backend shared library (no bundled runtime, `register_backend` left undefined) and confirmed that loading it against the installed `libexecutorch.so` registers the backend into the runtime's registry (`get_backend_class` goes from not-found to found). This is the mechanism that lets independently distributed backends coalesce into one runtime. - Confirmed the runner and the runtime link no libtorch/libc10 (via `ldd`). - Confirmed the Windows and macOS wheel code paths add nothing new, so those wheels are unaffected. - Lint and format pass (flake8, ufmt, cmake-format). Known limitation: the wheel-build step stores the SONAME symlinks as plain file copies rather than symlinks. Linking and loading still work because the SONAME target is present as a real file; a follow-up can preserve them as true symlinks to save space. ## CI Adds a PR job (test-cpp-sdk-wheel-linux in pull.yml, calling .ci/scripts/test_cpp_sdk_wheel.sh) that builds the wheel, installs it into a clean venv, and uses find_package(executorch) to build a C++ consumer linking executorch::runtime, then loads a coreless backend shared library and asserts it registers into libexecutorch.so. This gives the feature direct coverage: before, no PR job built the full wheel or linked the C++ SDK.

shoumikhin · 2026-07-29T21:05:44Z

Superseded by #21477, which submits the same change via ghstack so follow-up work can stack on top. Closing in favor of the ghstack version.

meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 29, 2026

shoumikhin force-pushed the sdk-cpp-wheel branch from d6aa74d to 86c35bd Compare July 29, 2026 20:34

shoumikhin force-pushed the sdk-cpp-wheel branch from 86c35bd to 1bc3075 Compare July 29, 2026 20:45

shoumikhin closed this Jul 29, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Ship a prebuilt C++ SDK in the ExecuTorch Linux wheel - #21470

Ship a prebuilt C++ SDK in the ExecuTorch Linux wheel#21470
shoumikhin wants to merge 1 commit into
pytorch:mainfrom
shoumikhin:sdk-cpp-wheel

shoumikhin commented Jul 29, 2026 •

edited

Loading

Uh oh!

pytorch-bot Bot commented Jul 29, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 29, 2026

Uh oh!

shoumikhin commented Jul 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

shoumikhin commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Why this is needed

What is inside

Why a shared library (not static archives)

How to use it

Test plan

CI

Uh oh!

pytorch-bot Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21470

❌ 33 New Failures, 160 Pending, 11 Unclassified Failures

Uh oh!

github-actions Bot commented Jul 29, 2026

This PR needs a release notes: label

Uh oh!

shoumikhin commented Jul 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

shoumikhin commented Jul 29, 2026 •

edited

Loading

pytorch-bot Bot commented Jul 29, 2026 •

edited

Loading

This PR needs a `release notes:` label