fix: alert users that darwin is not supported

[Mistobaan]

Summary

Add a note for the users that try to follow the tutorials on Apple/Darwin systems

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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:

• AWS was down, GHA infrastructure effected / recovering

❌ 7 New Failures, 3 Unrelated Failures

As of commit d5fa7d7 with merge base d2aa141 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 3f9d47fc85be3da50dc39b0996f8980e31f3e6af240be931fab5ab27e9179937 /exec failed with exit code 1
• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh)
  RuntimeError: Command docker exec -t 88cc2772d8ca5e56b4aff31ca11b473578e0651eb450fc86cbc67106e33fce55 /exec failed with exit code 1
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 838f28df3c08cf92b9f09ebf3b64e3819000ddec3acd93c1df4e3e5468a7dcfb /exec failed with exit code 1
• Test CUDA Builds / export-voxtral-cuda-non-quantized / linux-job (gh)
  RuntimeError: Command docker exec -t b2c6b0b1459c234a5e83e7e7b031e3313700247eeccd860138783fb051f3ba4f /exec failed with exit code 2
• Test CUDA Builds / export-voxtral-cuda-quantized-int4-tile-packed / linux-job (gh)
  RuntimeError: Command docker exec -t 10e8553ac2134f81820f4bc469041efcdcf1001536ef0838e76d3c8e2580ba7e /exec failed with exit code 2
• Test CUDA Builds / export-voxtral-cuda-quantized-int4-weight-only / linux-job (gh)
  RuntimeError: Command docker exec -t 1a0136e2024b94d60b7151510d02bf76fc8c8be4c7a5e4f44a929ace2fcb673a /exec failed with exit code 2
• Test Metal Backend / export-voxtral-metal-artifact / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / unittest / linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / android / run-emulator (gh) (trunk failure)
  The process '/usr/bin/sh' failed with exit code 255
• pull / unittest-editable / linux / linux-job (gh) (trunk failure)

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

[meta-cla]

Hi @Mistobaan!

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 [email protected]. Thanks!

[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.

[cccclai]

Thanks for contributing! We can merge after CI passes