Arm backend: Enable Vulkan validation layer

[wwwind]

Summary

Enable the Khronos Vulkan Validation Layer for the Arm VGF/VKML test paths.

The goal of this change is to detect invalid Vulkan API usage during VGF execution and make validation errors visible as CI failures, while keeping the production VGF runtime unchanged.

What this change does

• Enables VK_LAYER_KHRONOS_validation for VGF/VKML tests.

• Configures the validation layer through the Vulkan loader environment rather than modifying VkInstanceCreateInfo in the backend.

• Ensures the validation layer is placed before the Arm ML emulation layers.

• Makes the validation-layer manifest visible when the ML SDK overrides VK_LAYER_PATH.

• Restricts validation output to errors so warnings do not fail otherwise valid tests.

• Adds validation to both:

  • Python-based VKML execution through runner_utils.py.
  • Direct command paths such as examples/arm/run.sh and the VGF OOTB tests.

• Adds a wrapper for direct commands that converts Vulkan validation errors into a non-zero exit status.

• Preserves validation errors produced by earlier Vulkan subprocesses when a test launches multiple Vulkan processes.

• Keeps validation opt-in for generic pytest/Buck runs so environments without the Vulkan SDK or validation layer can still run the normal Arm test suite.

• Adds integration tests verifying that the validation layer is enabled and that validation failures are propagated correctly.

Validation can be controlled using:

EXECUTORCH_VGF_VULKAN_VALIDATION

The dedicated VGF/VKML test entry points enable it, while explicitly setting it to 0, false, off, or no disables validation for debugging.

Known validation errors

There are currently several validation errors produced by known issues in the VKML / Vulkan emulation-layer dependencies.

These VUIDs are temporarily filtered so that enabling Vulkan validation does not make the VGF CI permanently fail on already-known dependency bugs.

The filtered errors currently include issues related to:

• BF16 shader capability advertisement.
• Tensor-view usage validation.
• Descriptor layouts generated for duplicated custom-shader inputs.

The corresponding VUID filters are intentionally narrow so that any new or unexpected Vulkan validation error still fails the test.

These filters are temporary and should be removed individually once the corresponding bugs are fixed in the emulation-layer dependencies.

Why

Without the validation layer, invalid Vulkan API usage can remain unnoticed when running against the emulation layers. This change makes Vulkan API correctness part of the VGF/VKML CI signal and should help catch regressions closer to where they are introduced.

cc @SS-JIA @manuelcandales @digantdesai @cbilgin @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 4 Unrelated Failures

As of commit 64f511f with merge base 026ca3f ():

NEW FAILURE - The following job has failed:

• trunk / test-arm-backend-vkml (test_run_vkml) / linux-job (gh)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 134

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

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

• trunk / test-samsung-models-linux / linux-job (gh) (trunk failure)
  test_mobilebert_qat_a8w8
• trunk / unittest-release / linux / linux-job (gh) (trunk failure)
  [ FAILED ] ParallelTestWithOrWithoutThreadpool/ParallelTest.NestedCallsPreserveOuterThreadNumber/1, where GetParam() = false
• trunk / unittest-release / macos / macos-job (gh) (trunk failure)
  [ FAILED ] ParallelTestWithOrWithoutThreadpool/ParallelTest.NestedCallsPreserveOuterThreadNumber/1, where GetParam() = false
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  [ FAILED ] ParallelTestWithOrWithoutThreadpool/ParallelTest.NestedCallsPreserveOuterThreadNumber/1, where GetParam() = false

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