Rename build files from TARGETS to BUCK (group ID: 7266027221777385804)

[facebook-github-bot]

Reviewed By: bigfootjon

Differential Revision: D90811129

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures, 2 Cancelled Jobs, 1 Unrelated Failure

As of commit 08bdb64 with merge base b4b7837 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 1529372e714aa7247b957836194d8b03eb1f7b3b9a13db917b2d690787adcf61 /exec failed with exit code 3
• pull / unittest-buck / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3
• Test CUDA Builds / test-model-cuda-e2e (mistralai, Voxtral-Mini-3B-2507, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t 9d71021fdc8f937ba9432b3de192559d3a6551ac2b66cc8e72e157b46af57666 /exec failed with exit code 1

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• pull / test-static-llama-qnn-linux (stories_110m) / linux-job (gh)
  ##[error]The operation was canceled.
• pull / test-static-llama-qnn-linux (stories_260k_bc) / linux-job (gh)
  ##[error]The operation was canceled.

BROKEN TRUNK - The following job failed but were present on the merge base:

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

• pull / test-samsung-models-linux / linux-job (gh) (trunk failure)
  test_w2l_fp16

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

[meta-codesync]

@facebook-github-bot has exported this pull request. If you are a Meta employee, you can view the originating Diff in D90811129.

[bigfootjon]

Review automatically exported from Phabricator review in Meta.

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