Build PyTorch wheel via PEP 517 instead of setup.py - #21562
Conversation
Recent PyTorch nightlies removed support for "python setup.py bdist_wheel" and build through scikit-build-core (PEP 517) via pyproject.toml. The CI Docker image still built PyTorch with setup.py, so pinning to a newer nightly failed the image build. Build the wheel with the standard frontend (python -m build) with build isolation disabled, so PyTorch builds against the image's numpy and toolchain and reuses sccache. Install the PEP 517 build requirements explicitly since the frontend does not fetch them when isolation is off.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21562
Note: Links to docs will display an error until the docs builds have been completed. ❌ 3 New Failures, 5 Cancelled JobsAs of commit 9f5a15c with merge base 4b4df96 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOBS - The following jobs were cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
With build isolation off, scikit-build-core validates PyTorch's build requirements against the current environment and fails if setuptools, cmake or ninja are missing or too old. Install them alongside the other build requirements.
The unbounded cmake>=3.27 build requirement pulled cmake 4.4.2 into the conda env, which shadows the image cmake 3.31 and broke the Arm VGF runner build.
|
@JacobSzwejbka ping for a stamp when you get a chance. fresh ci run finished, the first one was wiped out by the actions outage on aug 6. on head 9f5a15c: 194 green including all 5 required checks, 5 cancellations, 3 failures. the 5 cancellations all died at "calculate docker image" while waiting on the image rebuild this pr triggers. no signal in them. the 3 failures are
all three pass on main. i read this as expected for a build change rather than a regression, but it is the one judgment call in this pr, so worth your eyes. |
…ay venv Re-land of #21562 with the leak fixed. The PEP 517 build requirements now go into a temporary virtualenv instead of the image conda environment, so scikit-build-core stops hijacking every later setuptools build in the image.
|
Heads up: this broke Not the cmake shadowing this PR guards against. Installing Revert: #21684. Re-land with the build requirements confined to a throwaway venv: #21685. |
Problem
Recent PyTorch nightlies removed
python setup.py bdist_wheel. PyTorch now builds through scikit-build-core using the standard PEP 517 interface (pyproject.toml). The CI Docker image still builds PyTorch withsetup.py, so bumping the pin to a newer nightly fails the image build with:Fix
Build the wheel with
python -m build --wheel --no-isolation:python -m buildis the standard PEP 517 frontend and works with PyTorch's scikit-build-core backend.--no-isolationmakes PyTorch build against the image'snumpyand toolchain (avoids a build-vs-runtime ABI mismatch) and lets the build reusesccache.[build-system].requires.The produced wheel still lands in
dist/, so the install step is unchanged.Testing
The Docker image build in this PR exercises the new build path end to end.