[ci-all][android] turn on USE_VULKAN for android builds by default

[IvanKobzarev]

ghstack-source-id: ae6ba19b0cb6313a04adbb39b192f44e220d2ce0
Pull Request resolved: #51291

Fixes #{issue number}

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit 6a15398 (more details on the Dr. CI page):

---

• 2/23 failures introduced in this PR
• 21/23 broken upstream at merge base 43f0ccd from Jan 28 until Jan 29

---

2 failures not recognized by patterns:

Job	Step	Action
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-gradle-build	pytorch android gradle build	🔁 rerun
pytorch_linux_xenial_py3_clang5_asan_test2	Set Up CI Environment After attach_workspace	🔁 rerun

---

🚧 21 fixed upstream failures:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

Check out the recency history of this "viable master" tracking branch.

• pytorch_windows_vs2019_py36_cpu_test1 from Jan 28 until Jan 29 (f2e4125 - 5a406c0)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cuda10.1_test1 from Jan 28 until Jan 29 (05c8cd7 - c096691)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cuda11.1_test1 from Jan 28 until Jan 29 (05c8cd7 - 5a406c0)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cuda10.1_test2 from Jan 28 until Jan 29 (05c8cd7 - c096691)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cpu_test2 from Jan 28 until Jan 29 (05c8cd7 - 5a406c0)
  • 🔁 rerun
• pytorch_linux_xenial_py3_6_gcc5_4_test from Jan 28 until Jan 29 (916af89 - 5a406c0)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_multigpu_test from Jan 28 until Jan 29 (916af89 - 5a406c0)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cuda10.1_on_cpu_test1 from Jan 28 until Jan 29 (f2e4125 - c096691)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_test2 from Jan 28 until Jan 29 (916af89 - 5a406c0)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_test1 from Jan 28 until Jan 29 (05c8cd7 - 5a406c0)
  • 🔁 rerun
• pytorch_linux_xenial_cuda11_1_cudnn8_py3_gcc7_test on Jan 28 from 8:31pm to 11:51pm (916af89 - 6e4746c)
  • 🔁 rerun
• pytorch_parallelnative_linux_xenial_py3_6_gcc5_4_test on Jan 28 from 7:30pm to 9:00pm (f2e4125 - 8a8fac6)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_nogpu_NO_AVX2_test on Jan 28 from 7:03pm to 9:19pm (e7b3496 - 5ed0ad4)
  • 🔁 rerun
• pytorch_windows_vs2019_py36_cuda11.1_test2 on Jan 28 from 7:30pm to 9:12pm (f2e4125 - 00d4ec8)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_slow_test on Jan 28 from 8:31pm to 11:32pm (916af89 - 6e4746c)
  • 🔁 rerun
• pytorch_linux_xenial_py3_clang5_asan_test1 from Jan 28 until Jan 29 (05c8cd7 - 5a406c0)
  • 🔁 rerun
• pytorch_paralleltbb_linux_xenial_py3_6_gcc5_4_test on Jan 28 from 7:30pm to 8:55pm (f2e4125 - 00d4ec8)
  • 🔁 rerun
• pytorch_linux_xenial_cuda9_2_cudnn7_py3_gcc7_test on Jan 28 from 7:30pm to 11:47pm (f2e4125 - 00d4ec8)
  • 🔁 rerun
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_nogpu_NO_AVX_test on Jan 28 from 7:03pm to 9:24pm (e7b3496 - 5ed0ad4)
  • 🔁 rerun
• pytorch_linux_bionic_py3_6_clang9_test on Jan 28 from 7:30pm to 8:47pm (f2e4125 - 8a8fac6)
  • 🔁 rerun
• pytorch_linux_xenial_py3_6_gcc7_test from Jan 28 until Jan 29 (43f0ccd - c096691)
  • 🔁 rerun

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

[AshkanAliabadi]

LGTM