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

[facebook-github-bot]

Reviewed By: bigfootjon

Differential Revision: D90809474

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

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

As of commit 8af61d3 with merge base 3341474 ():

NEW FAILURE - The following job has failed:

• Test CUDA Builds / test-model-cuda-e2e (mistralai, Voxtral-Mini-3B-2507, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t 5cdc7f34d328a11469b6af261ca0c203dd19f2745c8a9c4b32cc8d7c40d9dbea /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.

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-coreml-bc-macos (macos-m2-stable) / macos-job (gh) (matched macos rule in flaky-rules.json)
  File doesn't exist
• pull / test-models-linux (resnet50, xnnpack-quantization-delegation, linux.2xlarge) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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)
  ##[error]The operation was canceled.

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.

[meta-codesync]

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

[bigfootjon]

Review automatically exported from Phabricator review in Meta.