[ExecuTorch][WebGPU] Tests for the adamw WebGPU ops

[JCNTH]

Stack from ghstack (oldest at bottom):

• [ExecuTorch][WebGPU] Glob runtime/ops sources in CMakeLists #21005
• [ExecuTorch][Vulkan] Tests for et_vk.q4gsw_requant #20946
• [ExecuTorch][Vulkan] Add et_vk.q4gsw_requant kernel (STE re-quant to W_4X8) #20945
• [ExecuTorch][Vulkan] Tests for et_vk.linear_q4gsw_backward #20944
• [ExecuTorch][Vulkan] Add et_vk.linear_q4gsw_backward kernel (4-bit input-grad) #20943
• [ExecuTorch][Vulkan] Tests for et_vk.fused_ce #20942
• [ExecuTorch][Vulkan] Add et_vk.fused_ce kernels (fused cross-entropy loss + dlogits) #20941
• [ExecuTorch][Vulkan] Tests for et_vk.linear_dW #20940
• [ExecuTorch][Vulkan] Add et_vk.linear_dW kernel (dense fp32 weight-grad GEMM) #20939
• [ExecuTorch][Vulkan] Tests for et_vk.adamw_step #20938
• [ExecuTorch][Vulkan] Add et_vk.adamw_step kernel (on-GPU AdamW optimizer step) #20937
• -> [ExecuTorch][WebGPU] Tests for the adamw WebGPU ops #20936
• [ExecuTorch][WebGPU] Add et_vk.adamw_step (on-GPU AdamW optimizer step) to the WebGPU backend #20935
• [ExecuTorch][WebGPU] Tests for the fused_ce WebGPU ops #20934
• [ExecuTorch][WebGPU] Add et_vk.fused_ce (fused cross-entropy) to the WebGPU backend #20933
• [ExecuTorch][WebGPU] Tests for the q4gsw_train WebGPU ops #20932
• [ExecuTorch][WebGPU] Add q4gsw training kernels (backward, weight-grad, requant) to the WebGPU backend #20931
• [ExecuTorch][WebGPU] Tests for the shape_copy WebGPU ops #20930
• [ExecuTorch][WebGPU] Add shape/copy ops (dim_order, expand_copy, fill) to the WebGPU backend #20929
• [ExecuTorch][WebGPU] Tests for the gather WebGPU ops #20928
• [ExecuTorch][WebGPU] Add gather and embedding ops to the WebGPU backend #20927
• [ExecuTorch][WebGPU] Tests for the select_bool WebGPU ops #20926
• [ExecuTorch][WebGPU] Add select/boolean ops (where, scalar compares, logical_not) to the WebGPU backend #20925
• [ExecuTorch][WebGPU] Tests for the reduce WebGPU ops #20924
• [ExecuTorch][WebGPU] Add reduce op (sum/mean) to the WebGPU backend #20923
• [ExecuTorch][WebGPU] Tests for the binary WebGPU ops #20922
• [ExecuTorch][WebGPU] Add elementwise binary ops (div, sub) to the WebGPU backend #20921
• [ExecuTorch][WebGPU] Tests for the softmax WebGPU ops #20920
• [ExecuTorch][WebGPU] Add softmax ops (_softmax, _log_softmax) to the WebGPU backend #20919
• [ExecuTorch][WebGPU] Tests for the matmul WebGPU ops #20918
• [ExecuTorch][WebGPU] Add fp32 matmul ops (mm, bmm, linear) to the WebGPU backend #20917

Export-delegation + fp64 golden tests for the adamw (adamw_step) ops.

Key changes:

• test/ops/test_adamw.py — fp64 in-place param/m/v goldens (incl. non-zero weight-decay) + delegation checks — fp64 library-reference goldens + delegation checks (≥2 cases/op).

Co-authored-with: Claude Code.
@exported-using-ghexport

Differential Revision: D111755127

Differential Revision: D111755127

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ You can merge normally! (1 Unrelated Failure), 6 Unclassified Failures

As of commit af3b041 with merge base 21554e5 ():

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

• periodic / test-models-linux (buck2, mv3, portable, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory
• periodic / test-models-linux (buck2, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory
• periodic / test-models-linux (cmake, mv3, portable, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory
• periodic / test-models-linux (cmake, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory
• periodic / test-models-linux (cmake, vit, portable, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory
• periodic / test-models-linux (cmake, vit, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory

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-arm-backend-no-driver (test_pytest_models_tosa) / linux-job (gh) (trunk failure)

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.