Enable logging in MPS example runner builds

[sylvesterkaczmarek]

Fixes #12764.

The MPS example runner build defaults to Release, and ExecuTorch disables logging by default for non-Debug builds. As a result, runtime failures such as an invalid model path can exit without the ET_LOG diagnostics emitted by the runner.

Pass -DEXECUTORCH_ENABLE_LOGGING=ON when building the ExecuTorch runtime used by the MPS runner. This keeps Release optimization while retaining runtime diagnostics.

Validation: the current CMake preset sets EXECUTORCH_ENABLE_LOGGING off for Release builds and translates that to ET_LOG_ENABLED=0; runtime/platform/log.h enables logging when that define is not disabled. This change explicitly opts the runner build back into logging.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⚠️ 16 Awaiting Approval

As of commit a6a2b95 with merge base ed65b12 ():

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

• Build Aarch64 Linux Wheels (gh)
• Build documentation (gh)
• Build Linux Wheels (gh)
• Build macOS Wheels (gh)
• Build Presets (gh)
• Build Windows Wheels (gh)
• Lint (gh)
• periodic (gh)
• pull (gh)
• Test ARM Backend (gh)
• Test CoreML 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.

[meta-cla]

Hi @sylvesterkaczmarek!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[linux-foundation-easycla]

• ❌ - login: @sylvesterkaczmarek / name: Sylvester Kaczmarek. The commit (a6a2b95) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[sylvesterkaczmarek]

@pytorchbot label "release notes: examples"