Fix Zephyr CI cmake install failure by pinning to an existing PyPI version#18632
Fix Zephyr CI cmake install failure by pinning to an existing PyPI version#18632manuelcandales wants to merge 1 commit intomainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18632
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 27 PendingAs of commit 480c3c1 with merge base ad235f8 ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
There was a problem hiding this comment.
Pull request overview
This PR updates the Zephyr CI-driven setup instructions to pin cmake to a PyPI version that exists, addressing Zephyr trunk job failures caused by cmake==3.29 no longer being available on PyPI.
Changes:
- Update Zephyr requirements install command to use
cmake==3.29.6instead ofcmake==3.29.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cmake==3.29doesn't exist on PyPI anymore (currently existing versions are3.29.0.1,3.29.2, etc.), causing thetest-arm-backend-zephyrtrunk jobs to fail. Use3.29.6instead (the latest from the3.29series).