Build pip wheel and validate AOT workflow on different backends & host environments in CI #9019
Labels
module: build/install
Issues related to the cmake and buck2 builds, and to installing ExecuTorch
triaged
This issue has been looked at a team member, and triaged and prioritized into an appropriate module
🚀 The feature, motivation and pitch
We need to guard our AOT workflow in CI, to make sure our pip wheel can give users out-of-the-box user experience.
In CI we should cover the flow of:
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
cc @lucylq
The text was updated successfully, but these errors were encountered: