Arm backend: Update and enable ZephyrOS GitHub test #16539

zingo · 2026-01-12T12:36:02Z

Summary

This will test ZephyrOS by runing the commands in the README.md This verifies both the ZephyrOS support and make sure the instructions works.

Test plan

Include test in this PR

cc @freddan80 @per @oscarandersson8218 @digantdesai

This will test ZephyrOS by runing the commands in the README.md This verifies both the ZephyrOS support and make sure the instructions works. Signed-off-by: Zingo Andersen <[email protected]> Change-Id: I80a3cd658ff8e89fd52f0b934ea0bc3edc9da7dc

pytorch-bot · 2026-01-12T12:36:07Z

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16539

📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit cc05833 with merge base 7793b1d ():

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

pull / android / run-emulator (gh) (#16137)
Timeout waiting for emulator to boot.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

Set git user/email so setup.sh can be runned. Signed-off-by: Zingo Andersen <[email protected]> Change-Id: Ie9a7b0c1a7135434f578d07e6df44c18aba73bea

Signed-off-by: Zingo Andersen <[email protected]> Change-Id: Ib985416d356899e3edbc835b7468e95f2f6706e3

zingo · 2026-01-15T07:06:37Z

Hi @SS-JIA and @metascroy this PR touched files outside Arm/Zephyr stuff e.g. install_executorch.sh
so I think it would need a review for any of you, hope that is OK?

This tests will run the code snippets in the Zephyr README.md so both ZephyrOS integration is testsed and that the README.md is up to date and work :)

This removed dependancy to torchvision if not used as only the evaluator code need/uses it. Signed-off-by: Zingo Andersen <[email protected]> Change-Id: I4868945cd6957c898ec957daef004f48016945cb

Signed-off-by: Zingo Andersen <[email protected]> Change-Id: Ifee982a636472da756a2b1651ecd3842f8460a99

SS-JIA · 2026-01-20T16:54:44Z

install_executorch.sh

 #!/bin/bash
 # Copyright (c) Meta Platforms, Inc. and affiliates.
 # All rights reserved.
+# Copyright 2026 Arm Limited and/or its affiliates.


@mergennachin is this okay to add an arm copyright to this file?

yeah, that's fine. whenever an entity touches or makes changes to a file, they can append their copyright too

SS-JIA · 2026-01-20T16:58:14Z

install_executorch.sh

-cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null || /bin/true
+# Before doing anything, cd to the real path of the directory containing this script
+# so we avoid repeated symlink segments in downstream CMake paths.
+cd -- "$( realpath "$( dirname -- "${BASH_SOURCE[0]}" )" )" &> /dev/null || /bin/true


pretty sure this is okay

SS-JIA

install_executorch.sh LGTM - I believe that's the only change outside Arm

rascani · 2026-01-20T23:54:19Z

.github/workflows/trunk.yml

+        echo "===== Corstone300 FVP setup ===="
+
+        # Allowed only "export" command
+        run_command_block_from_zephyr_readme 'Config Zephyr Corstone300 FVP' '^export([[:space:]].*)$'
+
+        echo "---- Ethos-U55 ----"
+        rm -Rf build
+
+        # Allowed only "aot_arm_compiler" command
+        run_command_block_from_zephyr_readme 'Prepare the Ethos-U55 PTE model' '^python -m modules.lib.executorch.examples.arm.aot_arm_compiler([[:space:]].*)?$'
+
+        # Allowed only "west build" command
+        run_command_block_from_zephyr_readme 'Run the Ethos-U55 PTE model' '^west build([[:space:]].*)?$'
+
+        echo "---- Cortex-M55 ----"
+        rm -Rf build
+
+        # Allowed only "aot_arm_compiler" command
+        run_command_block_from_zephyr_readme 'Prepare the Cortex-M55 PTE model' '^python -m modules.lib.executorch.examples.arm.aot_arm_compiler([[:space:]].*)?$'
+
+        # Allowed only "west build" command
+        run_command_block_from_zephyr_readme 'Run the Cortex-M55 PTE model' '^west build([[:space:]].*)?$'
+
+        echo "===== Corstone320 FVP setup ===="
+
+        # Allowed only "export" command
+        run_command_block_from_zephyr_readme 'Config Zephyr Corstone320 FVP' '^export([[:space:]].*)$'
+
+        echo "---- Ethos-U85 ----"
+        rm -Rf build
+
+        # Allowed only "aot_arm_compiler" command
+        run_command_block_from_zephyr_readme 'Prepare the Ethos-U85 PTE model' '^python -m modules.lib.executorch.examples.arm.aot_arm_compiler([[:space:]].*)?$'
+
+        # Allowed only "west build" command
+        run_command_block_from_zephyr_readme 'Run the Ethos-U85 PTE model' '^west build([[:space:]].*)?$'


Is it possible to set these up as separate tests?

Yes, no problem, the setup time vs actual test time is the only downside as I see it. Can do it in this PR or in follow up PR?

zingo added the partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm label Jan 12, 2026

zingo requested a review from digantdesai as a code owner January 12, 2026 12:36

zingo added ciflow/trunk release notes: none Do not include this in the release notes labels Jan 12, 2026

meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 12, 2026

zingo mentioned this pull request Jan 14, 2026

Reenable test-models-arm-zephyr #13547

Open

Arm backend: Update and enable ZephyrOS GitHub test

6ae6502

Set git user/email so setup.sh can be runned. Signed-off-by: Zingo Andersen <[email protected]> Change-Id: Ie9a7b0c1a7135434f578d07e6df44c18aba73bea

zingo force-pushed the Arm-backend-Update-and-enable-ZephyrOS-GitHub-test branch from 3eb4c26 to 6ae6502 Compare January 14, 2026 07:14

zingo mentioned this pull request Jan 14, 2026

Zephyr SDK Version Bump v0.17.2->v0.17.3 #13426

Closed

zingo force-pushed the Arm-backend-Update-and-enable-ZephyrOS-GitHub-test branch 2 times, most recently from e336fc9 to 9965281 Compare January 14, 2026 12:30

Arm backend: Zephyr tests script print conda/venv to log

f6bb12b

Signed-off-by: Zingo Andersen <[email protected]> Change-Id: Ib985416d356899e3edbc835b7468e95f2f6706e3

zingo force-pushed the Arm-backend-Update-and-enable-ZephyrOS-GitHub-test branch 2 times, most recently from 5b7d845 to d55202a Compare January 15, 2026 06:19

Arm backend: aot compiler only import evaluator if needed

c1a2818

This removed dependancy to torchvision if not used as only the evaluator code need/uses it. Signed-off-by: Zingo Andersen <[email protected]> Change-Id: I4868945cd6957c898ec957daef004f48016945cb

zingo force-pushed the Arm-backend-Update-and-enable-ZephyrOS-GitHub-test branch from d55202a to c1a2818 Compare January 15, 2026 11:19

zingo and others added 2 commits January 15, 2026 16:10

Arm backend: remove Zephyr conda debug print

ceb8e60

Signed-off-by: Zingo Andersen <[email protected]> Change-Id: Ifee982a636472da756a2b1651ecd3842f8460a99

Fix typo in comment of test script

cc05833

SS-JIA reviewed Jan 20, 2026

View reviewed changes

SS-JIA approved these changes Jan 20, 2026

View reviewed changes

mergennachin requested review from larryliu0820, psiddh and rascani January 20, 2026 23:32

rascani reviewed Jan 20, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Arm backend: Update and enable ZephyrOS GitHub test #16539

Arm backend: Update and enable ZephyrOS GitHub test #16539

zingo commented Jan 12, 2026 •

edited by pytorch-bot bot

Loading

Uh oh!

pytorch-bot bot commented Jan 12, 2026 •

edited

Loading

Uh oh!

zingo commented Jan 15, 2026

Uh oh!

SS-JIA Jan 20, 2026

Uh oh!

mergennachin Jan 20, 2026

Uh oh!

SS-JIA Jan 20, 2026

Uh oh!

SS-JIA left a comment

Uh oh!

rascani Jan 20, 2026

Uh oh!

zingo Jan 21, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Arm backend: Update and enable ZephyrOS GitHub test #16539

Are you sure you want to change the base?

Arm backend: Update and enable ZephyrOS GitHub test #16539

Conversation

zingo commented Jan 12, 2026 • edited by pytorch-bot bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

pytorch-bot bot commented Jan 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16539

✅ You can merge normally! (1 Unrelated Failure)

Uh oh!

zingo commented Jan 15, 2026

Uh oh!

SS-JIA Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

mergennachin Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

SS-JIA Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

SS-JIA left a comment

Choose a reason for hiding this comment

Uh oh!

rascani Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

zingo Jan 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

zingo commented Jan 12, 2026 •

edited by pytorch-bot bot

Loading

pytorch-bot bot commented Jan 12, 2026 •

edited

Loading

zingo Jan 21, 2026 •

edited

Loading