Can we use ExecuTorch from cmake-out to export PTEs/PTDs for tests?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🐛 Describe the bug
I just had local test failures because I hadn't run install_executorch.sh in a while. The root cause seems to be that the add_custom_command CMake rules we use to export PTEs/PTDs, such as https://github.com/pytorch/executorch/blob/main/extension/flat_tensor/test/CMakeLists.txt#L25, use the installed version of ExecuTorch instead of the one we just built. Is is possible for us to point Python at the just-built ExecuTorch for these test export use cases so that people don't have to install ExecuTorch as part of the edit/compile/test loop for them?
Versions
main
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.
Research direction
Start with the add_custom_command rules in extension/flat_tensor/test/CMakeLists.txt and review install_executorch.sh to understand how test exports currently find ExecuTorch. Trace the PTE/PTD export path and verify that the test loop can use the just-built project without requiring an installation; confirm the relevant tests pass from a clean setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, python
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100