-
Couldn't load subscription status.
- Fork 701
CI Tests for Zephyr Integration #12734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12734
Note: Links to docs will display an error until the docs builds have been completed. ⏳ 2 Pending, 1 Unrelated FailureAs of commit 5e1a389 with merge base fead7c7 ( BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot label "release notes: none" |
0dbaafe to
03b8695
Compare
### Summary Previously the PAL file was uploaded as a placeholder for Zephyr apps to use. However, building `arm_zephyr.o` object was unsuccessful. The PAL has been updated and can now be used and linked to zephyr executorch applications. ### Test plan Tested on a simple add model arm executor runner, see [here](https://github.com/BujSet/zephyr/blob/5801a783883f3cf9bb172213d891c0de596c3dcf/samples/modules/executorch/arm-fvp-tutorials/models/CMakeLists.txt#L61) for a concrete example. CI tests are WIP, see [here](#12734).
03b8695 to
1521bb6
Compare
52b5bcb to
6220541
Compare
### Summary Previously the PAL file was uploaded as a placeholder for Zephyr apps to use. However, building `arm_zephyr.o` object was unsuccessful. The PAL has been updated and can now be used and linked to zephyr executorch applications. ### Test plan Tested on a simple add model arm executor runner, see [here](https://github.com/BujSet/zephyr/blob/5801a783883f3cf9bb172213d891c0de596c3dcf/samples/modules/executorch/arm-fvp-tutorials/models/CMakeLists.txt#L61) for a concrete example. CI tests are WIP, see [here](pytorch#12734).
b0c1cbc to
fe2dc9b
Compare
c244439 to
82f5381
Compare
82f5381 to
71a1983
Compare
ac0b406 to
8811a7e
Compare
…ectly to the trunk test
…ctory, moving all zpehyr stuff into the et repo (not ideal)
…scratch dir for zephyr CI tests (again, not ideal)
8811a7e to
5e1a389
Compare
Summary
Adding in CI tests to verify and maintain support for Zephyr projects that build executorch as a module. The main zephyr application source code is hosted externally for now, but the process to host an Executorch as an official module of zephyr is in progress.
This PR runs the simple Add model as unit tests, and verifies that the output is
2.0(1D tensor + 1D tensor, values filled with1.0s). This is intended to be a simple and fast test to exemplify how to use executorch to build an executor_runner for other models.Test plan
Added a new CI test called
test-models-arm-zephyrthat exits with status 0 on success, and 1 on failure.