JNI remove fbjni deps

[kirklandsign]

No description provided.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 7 New Failures, 4 Cancelled Jobs, 5 Unrelated Failures

As of commit e18fe7b with merge base 3090486 ():

NEW FAILURES - The following jobs have failed:

• Lint / android-java-format / linux-job (gh)
  RuntimeError: Command docker exec -t ba282723b3d12468f67622ab76ddc10ba4e01263ac2602d4c259ff4ffe04c08c /exec failed with exit code 1
• Lint / lintrunner / linux-job (gh)
  >>> Lint for extension/android/jni/jni_layer_training.cpp:
• pull / unittest-arm-backend-with-no-deps (test_pytest_models_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t 1b26a17ed3af133722ea97ce22a9652b246a5cbb0aa08a4dbd20473afe3e4614 /exec failed with exit code 127
• pull / unittest-arm-backend-with-no-deps (test_pytest_ops_no_target) / linux-job (gh)
  RuntimeError: Command docker exec -t 6bd6f752eb63536d6cc06b4e37f2928f6c807489f88f25e3c774e2522d9bd39f /exec failed with exit code 127
• pull / unittest-arm-backend-with-no-deps (test_pytest_ops_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t 0871d585c7a9fd99aa11dc1385a2ea9bf66a12e32052909ec947f2f2d5d83a68 /exec failed with exit code 127
• pull / unittest-arm-backend-with-no-deps (test_run_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t 873304e87a4661be3436ded21ab47bff0f5018f8b1c129683c87fb7a9c4fda7f /exec failed with exit code 127
• Test CUDA Builds / test-model-cuda-e2e (mistralai, Voxtral-Mini-3B-2507, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t 90ca2dfccf6bc6bafd2eee97c9abf9c483e38187c28932d49fe994de69b6e613 /exec failed with exit code 1

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

• pull / test-samsung-models-linux / linux-job (gh)
  ##[error]The operation was canceled.
• Test CUDA Windows Export / export-model-cuda-windows-artifact (google, gemma-3-4b-it, non-quantized) / linux-job (gh)
• Test CUDA Windows Export / export-model-cuda-windows-artifact (mistralai, Voxtral-Mini-3B-2507, quantized-int4-weight-only) / linux-job (gh)
• Test CUDA Windows Export / export-model-cuda-windows-artifact (openai, whisper-small, non-quantized) / linux-job (gh)

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

• Test CUDA Windows Export / export-model-cuda-windows-artifact (mistralai, Voxtral-Mini-3B-2507, non-quantized) / linux-job (gh) (matched win rule in flaky-rules.json)
  ##[error]The operation was canceled.
• Test CUDA Windows Export / export-model-cuda-windows-artifact (openai, whisper-large-v3-turbo, non-quantized) / linux-job (gh) (matched win rule in flaky-rules.json)
  ##[error]The operation was canceled.
• Test CUDA Windows Export / export-model-cuda-windows-artifact (openai, whisper-large-v3-turbo, quantized-int4-weight-only) / linux-job (gh) (matched win rule in flaky-rules.json)
  ##[error]The operation was canceled.
• Test CUDA Windows Export / export-model-cuda-windows-artifact (openai, whisper-small, quantized-int4-weight-only) / linux-job (gh) (matched win rule in flaky-rules.json)
  ##[error]The operation was canceled.

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)
  Timeout waiting for emulator to boot.

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

[kirklandsign]

@copilot Help me remove other fbjni dependencies from build.gradle

[Copilot]

@kirklandsign I've opened a new pull request, #16554, to work on those changes. Once the pull request is ready, I'll request review from you.

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