[ExecuTorch][WebGPU] Op-tests for the 10 unary activations#21155
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21155
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ You can merge normally! (1 Unrelated Failure)As of commit 40e3cf6 with merge base 266e0dc ( BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
psiddh
left a comment
There was a problem hiding this comment.
Approving full WebGPU stack
Stack from ghstack (oldest at bottom):
Adds the declarative op-test suites for the unary activations ported in the diff below. Each op gets a
torchreference plus a deterministic, range-bounded input so the fp64 golden is well-defined — positive forsqrt/rsqrt, spanning the ±3 knees forhardswish, and reaching the ±15 clamp fortanh— driving the manifest-based Dawn golden.Key changes:
test/ops/test_unary_activations.py—UnaryModule+UNARY_G1(op name -> torch fn + linspace input gen).test/op_tests/cases.py— registers the 10 suites (amat+ arank3case each) via a factory loop, mirroring the existing per-op registration convention.Differential Revision: D112257657