Cortex-M backend: add cortex-m0plus to the trunk e2e CI matrix#19774
Open
rascani wants to merge 8 commits into
Open
Cortex-M backend: add cortex-m0plus to the trunk e2e CI matrix#19774rascani wants to merge 8 commits into
rascani wants to merge 8 commits into
Conversation
Extends `_test_cortex_m_e2e.yml` with a `targets` input that joins the existing `model` matrix to give a target × model cross product, so trunk can exercise the same suite against multiple Cortex-M variants. The trunk job opts in to `["cortex-m55", "cortex-m0plus"]`; the nightly job (and any future caller that doesn't pass `targets`) falls back to the M55-only default and keeps its current shape. Cortex-M0+ is the first scalar-class (Armv6-M) variant to enter CI. It exercises the pure-C CMSIS-NN kernel path (`__ARM_FEATURE_DSP` and `__ARM_FEATURE_MVE` both undefined), covering the M0+ enablement patches that fix the Armv6-M HardFault handler and the `ARMCM0plus` directory-case mismatch in the Cortex DFP. M0, M3, and M23 share the same Armv6-M / Armv8-M Baseline arch family and can slot into the same `targets` array later without further workflow changes. `pull.yml`'s `test-mcu-cortex-m-backend` is intentionally left at M55-only — per-PR coverage is deferred until the trunk M0+ leg demonstrates stability over a few cycles. Authored with Claude.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19774
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 2 Unclassified FailuresAs of commit c0cf171 with merge base 26b4be8 ( NEW FAILURE - The following job has failed:
UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
digantdesai
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends
_test_cortex_m_e2e.ymlwith atargetsinput that joins the existingmodelmatrix to give a target × model cross product, so trunk can exercise the same suite against multiple Cortex-M variants. The trunk job opts in to["cortex-m55", "cortex-m0plus"]; the nightly job (and any future caller that doesn't passtargets) falls back to the M55-only default and keeps its current shape.Cortex-M0+ is the first scalar-class (Armv6-M) variant to enter CI. It exercises the pure-C CMSIS-NN kernel path (
__ARM_FEATURE_DSPand__ARM_FEATURE_MVEboth undefined), covering the M0+ enablement patches that fix the Armv6-M HardFault handler and theARMCM0plusdirectory-case mismatch in the Cortex DFP. M0, M3, and M23 share the same Armv6-M / Armv8-M Baseline arch family and can slot into the sametargetsarray later without further workflow changes.Test plan
CI
Authored with Claude.