[AxelNoun]

Summary

nxp-mcuxpresso-test is red on main and on every pull request, for a reason that has nothing to do with the code under test.

test_build_from_scratch.sh ran west init against mcuxsdk-manifests without a revision, so the job followed that repository's default branch — a moving target tracking the unreleased 26.12.00 SDK. That branch pins the fw_bin project to NXP/wifi_nb_fw@2553ab1d2097f0adb6e0846f054142c86045db3f, a commit the remote no longer serves. Because the project is declared with clone-depth: 1, west fetches that exact SHA and has no fallback:

fatal: remote error: upload-pack: not our ref 2553ab1d2097f0adb6e0846f054142c86045db3f
ERROR: update failed for project fw_bin
FATAL ERROR: Command failed: Update failed

This pins the manifest to v26.09.00, the most recent tag whose fw_bin revision still resolves (ae66e11f). The v26.12.00-pvw1 tag carries the same dangling pin as the default branch, so it is not an option. MCUXSDK_MANIFEST_REV lets the revision be overridden, matching how ARM_TOOLCHAIN_URL is already handled in the same script.

Beyond unbreaking the job, pinning removes a standing dependency on an upstream branch that can change under us at any time.

What was checked

• The dangling SHA is genuinely absent from NXP/wifi_nb_fw (GitHub returns 422 No commit found for SHA).
• At v26.09.00, every SDK path this example's CMakeLists.txt consumes exists: eiq_examples/executorch_cifarnet/{main.cpp,RegisterKernels.cpp}, eiq_examples/common/timer.c, _boards/mimxrt700evk/eiq_examples/executorch_cifarnet/cm33_core0/{hardware_init.c,pin_mux.c,gcc/MIMXRT798Sxxxx_cm33_core0_flash.ld} and .../npu.
• Between v26.09.00 and the default branch, mcuxsdk-middleware-executorch advances by exactly one commit, a documentation URL fix — so the pin gives up nothing on the ExecuTorch side.

What was not checked

The full ARM build was not reproduced locally, so that the example still links against the September SDK rests on the file-level checks above rather than on an actual build. CI on this PR is the real verification.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Investigating a potential degradation on Meta's CI clusters

⚠️ 24 Awaiting Approval

As of commit 1814227 with merge base ec56cfa ():

AWAITING APPROVAL - The following workflows need approval before CI can run:

• Build Aarch64 Linux CUDA Wheels (gh)
• Build Aarch64 Linux Native Wheels (gh)
• Build Aarch64 Linux Wheels (gh)
• Build documentation (gh)
• Build Linux CUDA Wheels (gh)
• Build Linux Native Wheels (gh)
• Build Linux Wheels (gh)
• Build macOS Wheels (gh)
• Build Presets (gh)
• Build Windows Wheels (gh)
• Cadence Build & Test (gh)
• Lint (gh)
• periodic (gh)
• pull (gh)
• Test ARM Backend (gh)
• Test CoreML Backend (gh)
• Test Cortex-M Backend (gh)
• Test CPU Backend (gh)
• Test NXP Backend (gh)
• Test QNN Backend (gh)
• Test QNN Windows MSVC build (gh)
• Test Vulkan Backend (gh)
• Test WebGPU Backend (gh)
• Test XNNPACK Backend (gh)

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.