Build pip wheel and validate AOT workflow on different backends & host environments in CI
Open
@jathu is already working on this.
Since Mar 6, 2025.
module: build/install
triaged
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🚀 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:
- Build pip wheel on PR or trunk, for MacOS or Linux
- This exists right now but need to leverage the artifact in following steps.
- Install pip wheel
- Export a simple model (MV3) with common backend delegation (XNNPACK, Coreml, QNN) and retrieve .pte files
- Load the .pte files in python and run sample input (optional, depend on feasibility)
| macOS (P0) | Linux (P0) | Windows (P1) | |
|---|---|---|---|
| XNNPACK |
|
|
|
| CoreML |
|
|
Not applicable |
| QNN | Not applicable |
|
|
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
cc @lucylq
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.